[Evolution] Bug#400965: 'Failed to read a valid object file image from memory'

[Øystein Gisnås]

2006/12/3, Sam Morris <sam at robots.org.uk>:
> On Sun, 2006-12-03 at 23:21 +0100, Øystein Gisnås wrote:
> > 2006/11/30, Sam Morris <sam at robots.org.uk>:
> > > NB, bug-buddy (or gdb) spits out "Failed to read a valid object file
> > > image from memory" to the console.
> >
> > Sorry, didn't see this. If you can reproduce the bug, I would have
> > tried to run evolution from gdb instead of connecting to it later
> > (like bug-buddy does).
>
> Ok, I'll try that.
>
> I have done some experimentation with gdb and other programs. It seems
> it *always* fails in this way. This makes backtraces and breakpoints
> useless (I can set them but they are never triggered).
>
> Evolution just froze when I tried to send this message! But this is
> another bug that I've been seeing for some time: "Evolution freezes when
> run under gdb and it spawns an external process such as gpg". I haven't
> reported _that_ bug yet because:
>
> <freeze>
> Cannot find thread 213003: invalid thread handle
> (gdb) where
> Cannot find thread 213003: invalid thread handle
> Cannot find thread 213003: invalid thread handle
> (gdb) kill
> Kill the program being debugged? (y or n) y
> <gdb freezes too>
> <sam throws brick at computer>
>
> I guess I'll file a bug against gdb and hope the maintainers of that
> package can help me nurse it back to health!

That would be nice. It might be evolution's fault, but to debug the
debugger, some magic is required that I don't possess.