gvfsd-fuse crashed with SIGSEGV in calloc()

Bug #1054817 reported by Michael Gratton
10
This bug affects 1 person
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
ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
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/gvfs/gvfsd-fuse
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcCmdline: /usr/lib/gvfs//gvfsd-fuse -f /home/username/.gvfs
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_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 calloc () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib64/ld-linux-x86-64.so.2
 ?? () from /lib64/ld-linux-x86-64.so.2
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

Revision history for this message
Michael Gratton (mjog) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

visibility: private → public
tags: removed: need-amd64-retrace
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.