fish crashed with SIGSEGV in __GI__IO_wfile_xsputn()

Bug #1665822 reported by Eustachy motyka
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
fish (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

app error after system crash

ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: fish 2.4.0-1
ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
Uname: Linux 4.9.0-15-generic i686
ApportVersion: 2.20.4-0ubuntu2
Architecture: i386
CrashCounter: 1
Date: Fri Feb 10 18:27:53 2017
ExecutablePath: /usr/bin/fish
ExecutableTimestamp: 1481423198
InstallationDate: Installed on 2015-09-22 (514 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150917)
ProcCmdline: fish
ProcCwd: /home/ytrew8
ProcEnviron:
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
 TERM=linux
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
Signal: 11
SourcePackage: fish
StacktraceTop:
 __GI__IO_wfile_xsputn (f=0xb751cd60 <_IO_2_1_stdout_>, data=0x8019b1b0, n=4) at wfileops.c:1027
 _IO_vfwprintf (s=<optimized out>, format=0x8164d888 L"%ls: %ls'%ls' terminated by signal %ls (%ls)", ap=0xbfe89650 "Ė迀\336k\201̂\033\200@\346h\201\244f\033\200\003") at vfprintf.c:1637
 __fwprintf_chk (fp=0xb751cd60 <_IO_2_1_stdout_>, flag=1, format=0x8164d888 L"%ls: %ls'%ls' terminated by signal %ls (%ls)") at fwprintf_chk.c:35
 job_reap(bool) ()
 parse_execution_context_t::run_1_job(parse_node_t const&, block_t const*) ()
Title: fish crashed with SIGSEGV in __GI__IO_wfile_xsputn()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo

Revision history for this message
Eustachy motyka (eustachy1) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __GI__IO_wfile_xsputn (f=0xb751cd60 <_IO_2_1_stdout_>, data=0x8019b1b0, n=4) at wfileops.c:1027
 _IO_vfwprintf (s=<optimized out>, format=0x8164d888 L"%ls: %ls'%ls' terminated by signal %ls (%ls)", ap=0xbfe89650 "\304\226\350\277\200\336k\201\314\202\033\200@\346h\201\244f\033\200\003") at vfprintf.c:1637
 __fwprintf_chk (fp=0xb751cd60 <_IO_2_1_stdout_>, flag=1, format=0x8164d888 L"%ls: %ls'%ls' terminated by signal %ls (%ls)") at fwprintf_chk.c:35
 job_reap(bool) ()
 parse_execution_context_t::run_1_job(parse_node_t const&, block_t const*) ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in fish (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Marc Deslauriers (mdeslaur) wrote : Bug is not a security issue

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

information type: Private Security → Public
Revision history for this message
Kurtis Rader (krader) wrote :

I am a fish developer. What version of fish are you using? What does `locale` report? Steps to reproduce? Can you set `ulimit -c unlimited` and reproduce the problem to get a core dump for analysis? Note that we recently made several changes to avoid mixing narrow and wide stdio calls which can lead to unpredictable behavior so the fish version you're using is important. Also, since it is more likely this is a fish bug than a Ubuntu specific bug it will probably be more fruitful to open an issue against the fish project: https://github.com/fish-shell/fish-shell/issues/new

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in fish (Ubuntu):
status: New → Confirmed
Revision history for this message
Niklas Sombert (ytvwld) wrote :

I think I'm affected by the same bug. The weird thing is: I think I only get this when starting Atom but I'm not sure.

It sure doesn't crash one of the shells I'm actively using. I just get the "an application on your system has crashed" dialog.

$ locale
LANG=de_DE.UTF-8
LANGUAGE=
LC_CTYPE="de_DE.UTF-8"
LC_NUMERIC="de_DE.UTF-8"
LC_TIME="de_DE.UTF-8"
LC_COLLATE="de_DE.UTF-8"
LC_MONETARY="de_DE.UTF-8"
LC_MESSAGES="de_DE.UTF-8"
LC_PAPER="de_DE.UTF-8"
LC_NAME="de_DE.UTF-8"
LC_ADDRESS="de_DE.UTF-8"
LC_TELEPHONE="de_DE.UTF-8"
LC_MEASUREMENT="de_DE.UTF-8"
LC_IDENTIFICATION="de_DE.UTF-8"
LC_ALL=

Revision history for this message
Niklas Sombert (ytvwld) wrote :

(um, I'm on 18.04.4 amd64)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.