GNOME Bugzilla – Bug 609779
gvfsd-sftp crashed with SIGSEGV in g_hash_table_iter_init()
Last modified: 2010-04-14 13:35:06 UTC
Originally reported at: https://bugs.edge.launchpad.net/bugs/517260 Binary package hint: gvfs I had mounted a share via SSH using Gnome's "Connect to Server" under places. I got the error a few seconds after unmounting the volume. ProblemType: Crash Architecture: amd64 CrashCounter: 1 Date: Thu Feb 4 15:51:08 2010 DistroRelease: Ubuntu 10.04 ExecutablePath: /usr/lib/gvfs/gvfsd-sftp InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100113) Package: gvfs-backends 1.5.2-0ubuntu2 ProcCmdline: /usr/lib/gvfs/gvfsd-sftp --spawner :1.5 /org/gtk/gvfs/exec_spaw/3 ProcEnviron: SHELL=/bin/bash LANG=en_CA.UTF-8 ProcVersionSignature: Ubuntu 2.6.32-12.16-generic SegvAnalysis: Segfault happened at: 0x7f566af2bb91 <g_hash_table_iter_init+17>: mov 0x34(%rsi),%eax PC (0x7f566af2bb91) ok source "0x34(%rsi)" (0xaaaaaaaaaaaaaade) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gvfs StacktraceTop: g_hash_table_iter_init () from /lib/libglib-2.0.so.0 ?? () ?? () ?? () from /usr/lib/libgio-2.0.so.0 ?? () from /usr/lib/libgio-2.0.so.0 Title: gvfsd-sftp crashed with SIGSEGV in g_hash_table_iter_init() Uname: Linux 2.6.32-12-generic x86_64 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance! Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
downstream reporters are stating that this bug is fixed with newest release, marking this as fixed, thanks.