gvfsd-fuse crashed with SIGSEGV in calloc()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gvfs (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Wasn't using any GFVS volume at the time, was messing with a Samba server on the same network though.
> mjg@montbard:~$ ls -l .gvfs
> ls: cannot access .gvfs: Transport endpoint is not connected
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: gvfs-fuse 1.13.9-0ubuntu1
ProcVersionSign
Uname: Linux 3.5.0-15-generic x86_64
ApportVersion: 2.5.2-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Sat Sep 22 18:21:17 2012
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcCmdline: /usr/lib/
SegvAnalysis:
Segfault happened at: 0x7fe1600b1778: mov 0x8(%r12),%r15
PC (0x7fe1600b1778) ok
source "0x8(%r12)" (0xffc2b8ec07aa) not located in a known VMA region (needed readable region)!
destination "%r15" ok
Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
?? () from /lib/x86_
?? () from /lib/x86_
calloc () from /lib/x86_
?? () from /lib64/
?? () from /lib64/
Title: gvfsd-fuse crashed with SIGSEGV in calloc()
UpgradeStatus: Upgraded to quantal on 2012-09-18 (4 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1054041, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.