Bug#707681: Happens also with 1.18.2-1
Emilio Pozuelo Monfort
pochu at debian.org
Wed Oct 30 15:24:16 UTC 2013
On 30/10/13 15:48, Yves-Alexis Perez wrote:
> On Wed, 2013-10-30 at 11:16 +0100, Emilio Pozuelo Monfort wrote:
>> On 30/10/13 09:13, Yves-Alexis Perez wrote:
>>> Is someone actually looking at bug reports and can investigate if it's a
>>> problem in gvfs, in libusb or elsewhere?
>>
>> Get a gdb backtrace with debugging symbols (the one in the bug report is
>> useless), and ideally send it to bugzilla.gnome.org.
>>
> Can you indicate how to do that, considering I have no idea how exactly
> the binary is run?
get a core file, or attach to the process while it's running, or if it's
crashing just after it's spawned, patch it to have a sleep or an infinite loop
right at startup and then after you attach with gdb you change the variable so
it exits the loop and continues. Or maybe just run gvfsd or
gvfs-gphoto2-volume-monitor under gdb and follow the child (I'm not sure who's
launching gvfsd-gphoto2 so not sure if the latter would work).
More information about the pkg-gnome-maintainers
mailing list