sshfs crashed with SIGSEGV

[the_one(2)]

sshfs crashed when I copied a 40 GB folder (8 GB had been successfully copied before the crash) with nautilus

ProblemType: Crash
Architecture: i386
Date: Sat Apr 5 21:33:31 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/sshfs
Package: sshfs 1.7-2.1
PackageArchitecture: i386
ProcCmdline: sshfs -p 37252 nas@192.168.0.106:/mnt/nas/raid /home/hostname/NAS/
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=sv_SE.UTF-8
Signal: 11
SourcePackage: sshfs-fuse
Stacktrace:
 #0 0x0804f37c in ?? ()
 #1 0xb7e2ef55 in ?? () from /usr/lib/libglib-2.0.so.0
 #2 0xb58070d0 in ?? ()
 #3 0x00000000 in ?? ()
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/libglib-2.0.so.0
 ?? ()
 ?? ()
Title: sshfs crashed with SIGSEGV
Uname: Linux 2.6.24-12-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video
SegvAnalysis:
 Segfault happened at: 0x804f37c <sem_init@plt+22748>: cmp 0x74(%eax),%edx
 PC (0x0804f37c) ok
 source "0x74(%eax)" (0x00000074) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA

[Apport retracing service (apport)]

StacktraceTop:cache_clean () at cache.c:74
cache_add_attr (
cache_getattr (path=0x8055628 "%", stbuf=0xb7c341e0)
fuse_fs_getattr (fs=0x8055ff8,
fuse_lib_getattr (req=0xb5a132d0, ino=1745, fi=0x0)

[Charlie Kravetz (cjkgeek)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Lucid Lynx. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.

This should be fixed in the version of sshfs in Lucid Lynx.

[Charlie Kravetz (cjkgeek)]

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Ubuntu 10.04 was released on 2010-04-29. Thanks!

[Charlie Kravetz (cjkgeek)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!