"brian m. carlson" <[EMAIL PROTECTED]> writes:
> On Sat, Sep 06, 2008 at 06:39:42PM +0200, Goswin von Brederlow wrote:
>>could you please run gvfs-fuse with debug enabled (-d) and append the
>>last hundred lines or so?
>
> The lines are below. Note that a segfault occurs.
>
> OPEN[22286752] flags: 0x8002 /sftp on
> castro/media/data/bmc/finished/music/AlkalineTrio-Burn.mp3
> unique: 6019, opcode: READ (15), nodeid: 2121, insize: 80
> READ[22286752] 16384 bytes from 0
> READ[22286752] 16384 bytes
> unique: 6019, error: 0 (Success), outsize: 16400
> unique: 6020, opcode: GETATTR (3), nodeid: 2121, insize: 56
> unique: 6020, error: 0 (Success), outsize: 112
> unique: 6021, opcode: READ (15), nodeid: 2121, insize: 80
> READ[22286752] 4096 bytes from 5971968
> READ[22286752] 2593 bytes
> unique: 6021, error: 0 (Success), outsize: 2609
> unique: 6022, opcode: GETATTR (3), nodeid: 2121, insize: 56
> unique: 6022, error: 0 (Success), outsize: 112
> unique: 6023, opcode: READ (15), nodeid: 2121, insize: 80
> READ[22286752] 32768 bytes from 16384
> unique: 6024, opcode: OPEN (14), nodeid: 2121, insize: 48
> zsh: segmentation fault /usr/lib/gvfs//gvfs-fuse-daemon -d
> /home/bmc/.gvfs 2>&1 | zsh: done tee /tmp/foo
I thought something like that happened. That is usualy the case for a
fuse filesystem to just disconnect.
Could you run
gdb /usr/lib/gvfs//gvfs-fuse-daemon
r /home/bmc/.gvfs
get it to segfault and then get a stack backtrace (bt) to see where it
segfaults. The best would be if you could compile gvfs-fuse with
export DEB_BUID_OPTIONS=nostrip
dpkg-buildpackage
which should keep the debug infos in the binaries.
MfG
Goswin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
