> Also, sprach Miklos Szeredi am Freitag, den 29. Dezember 2006 um 15:11: > > OK, that implicates fuse, rather than sshfs. The following patch > > removes an unalinged access in that part of the code. Can you > > please try compiling fuse with this patch? > > I applied the patch to the fuse source (retrieved via apt-get source > fuse, version is 2.5.3-4.1) like this: > > $ patch -p0 < /home/smc/fuse.diff=20 > patching file lib/mount.c > Hunk #1 succeeded at 133 with fuzz 2 (offset -20 lines). > Hunk #2 succeeded at 163 with fuzz 1 (offset -20 lines). > > The applied patches look correct nevertheless. I then built the > package with > > $ dpkg-buildpackage -b -rfakeroot -us -uc > > and installed the debs for fuse-utils and libfuse2 (libfuse-dev was > not installed and if I am not completely mistaken is irrelevant either > way). > > I repeated the gdb steps but the same errors (bus access error, > mountpoint unusable and has weird permissions) and kernel messages > (see below), and the output looks conspicuously the same (n.b.: to be > absolutely sure I restarted the machine first): > > $ gdb sshfs > GNU gdb 6.4.90-debian > Copyright (C) 2006 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you = > are > welcome to change it and/or distribute copies of it under certain conditi= > ons. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for detail= > s. > This GDB was configured as "sparc-linux-gnu"...Using host libthread_db li= > brary "/lib/v9/libthread_db.so.1". > =20 > (gdb) set args [EMAIL PROTECTED]:/home/smc phobos/ > (gdb) run > Starting program: /usr/bin/sshfs [EMAIL PROTECTED]:/home/smc phobos/ > [Thread debugging using libthread_db enabled] > [New Thread 16384 (LWP 4600)] > =20 > Program received signal SIGBUS, Bus error. > [Switching to Thread 16384 (LWP 4600)] > 0xf7f9f0c8 in fuse_mount_compat22 () from /usr/lib/libfuse.so.2 > (gdb) backtrace > #0 0xf7f9f0c8 in fuse_mount_compat22 () from /usr/lib/libfuse.so.2 > #1 0xf7f9f338 in fuse_mount () from /usr/lib/libfuse.so.2 > #2 0xf7f9ea00 in fuse_parse_cmdline () from /usr/lib/libfuse.so.2 > #3 0xf7f9eb88 in fuse_setup_compat22 () from /usr/lib/libfuse.so.2 > #4 0x000191a0 in main (argc=3D3, argv=3D0xff9b55d4) at sshfs.c:2514 > (gdb) The program is running. Exit anyway? (y or n) y
I don't know what else could it be. Can you compile fuse with debugging enabled (DEB_BUILD_OPTS=nostrip,noopt) and repeat the experiment? The backtrace should then give a more detailed analysis. Thanks, Miklos -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
