I think that gphoto2_backend->lock is also not NULL, as g_mutex_clear()
derefs it: g_mutex_impl_free (mutex->p); it seems it's
gphoto2_backend->lock->p which is NULL then, i. e. the mutex was not
initialized properly.
The only access to this aside from the _lock()/_unlock() calls is in
do_mount() line 1715, i. e. it gets initialized _after_ release_device()
is called (which tries to free it again).
** Changed in: gvfs (Ubuntu Precise)
Status: Confirmed => In Progress
** Changed in: gvfs (Ubuntu Precise)
Assignee: Canonical Desktop Team (canonical-desktop-team) => Martin Pitt
(pitti)
--
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
