[neuron <neuron@ho...>]

Hi

I've done some major changes in my code, and after them I get some 
valgrind errors on unmount.

if I do mount then immediatly umount (or any operation in between) I get:

==20247== Invalid read of size 8
==20247==    at 0x119106A4: (within /lib/ld-2.3.5.so)
==20247==    by 0x119089BC: (within /lib/ld-2.3.5.so)
==20247==    by 0x11904DF3: (within /lib/ld-2.3.5.so)
==20247==    by 0x11906612: (within /lib/ld-2.3.5.so)
==20247==    by 0x11F4C16B: (within /lib/libc-2.3.5.so)
==20247==    by 0x1190B13F: (within /lib/ld-2.3.5.so)
==20247==    by 0x11F4CD19: _dl_open (in /lib/libc-2.3.5.so)
==20247==    by 0x11F4E1C7: (within /lib/libc-2.3.5.so)
==20247==    by 0x1190B13F: (within /lib/ld-2.3.5.so)
==20247==    by 0x11F4E272: __libc_dlopen_mode (in /lib/libc-2.3.5.so)
==20247==    by 0x12098BCB: pthread_cancel_init (in 
/lib/libpthread-2.3.5.so)
==20247==    by 0x12095867: pthread_cancel (in /lib/libpthread-2.3.5.so)


What I'm curius about is that this happens between fusermount -u 
<directory> and before the destroy event is triggered, could someone 
tell me where I should start debugging this?

As it happens only on umount, and before the destroy event, so I'm a bit 
unsure about where it's coming from.

n