gvfsd-smb-browse crashed with SIGSEGV in debug_add_class()

Bug #919544 reported by Greg A
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
New
Undecided
Unassigned

Bug Description

Crash occured after clicking on "Browse Network" from within Nautilus

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gvfs-backends 1.10.1-1ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-9.16-generic 3.2.1
Uname: Linux 3.2.0-9-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Sat Jan 21 07:57:54 2012
ExecutablePath: /usr/lib/gvfs/gvfsd-smb-browse
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120112)
ProcCmdline: /usr/lib/gvfs/gvfsd-smb-browse --spawner :1.9 /org/gtk/gvfs/exec_spaw/3
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f38a8238f39: mov (%r14,%rbx,8),%rsi
 PC (0x7f38a8238f39) ok
 source "(%r14,%rbx,8)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rsi" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libsmbclient.so.0
 debug_add_class () from /usr/lib/x86_64-linux-gnu/libsmbclient.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libsmbclient.so.0
 setup_logging () from /usr/lib/x86_64-linux-gnu/libsmbclient.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libsmbclient.so.0
Title: gvfsd-smb-browse crashed with SIGSEGV in debug_add_class()
UpgradeStatus: Upgraded to precise on 2012-01-13 (7 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Greg A (etulfetulf) 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 #911888, 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
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.