This stack trace makes little sense. In do_mount(), we see that the
gphoto2_backend is initialized:
gphoto2_backend = 0x9930e0
A few lines before release_device (gphoto2_backend) it even dereferences
gphoto2_backend->camera, and that did not give a segfault, so at that
point gphoto2_backend was still valid. But at this call, the stack trace
claims
#2 0x00000000004058c5 in release_device (gphoto2_backend=0x0) at
gvfsbackendgphoto2.c:621
This cannot be true, before line 621 release_device() derefs
gphoto2_backend dozens of times. So that 0x0 is wrong.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/968186
Title:
gvfsd-gphoto2 crashed with SIGSEGV in __pthread_mutex_destroy()
To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/968186/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
