Problems with multi-threaded application debugging

Ulisses Furquim ulissesf@gmail.com
Thu May 31 18:35:00 GMT 2007


Hi Daniel,

On 5/31/07, Daniel Jacobowitz <drow@false.org> wrote:
> > - sometimes when you "continue" gdb doesn't stop at a breakpoint
> > inside some of the threads;
> > - sometimes when you try to single step (with "next") all the threads
> > run until the program exits;
>
> I have no idea what these might be.

Yeah, I thought it was really strange and I can trigger this behavior
with a really simple application.

> > - I was trying to use the scheduler-locking variable (setting it to
> > "on"), but it seems I can single step on only one thread. I mean, If I
> > switch to another thread and try to single step it, gdb switches back
> > to the previous thread.
>
> To be honest, I can't completely remember whether this is supposed to
> happen still or supposed to be fixed.  You need to be using a current
> version of gdb and gdbserver, but GDB may still be doing something
> wrong.

Ah, I'm sorry, I wasn't completely clear. I forgot to say that I can
trigger all those problems with gdb 6.4-debian (from Ubuntu Edgy) on a
x86 machine and also with gdb 6.6 on an ARM device. I'm not even using
gdbserver (yet).

Regards,

-- Ulisses



More information about the Gdb mailing list