Re: [SPAM] Re: gdbserver signals interfere with {next,step{,i}}

[Jon Ringle <jon at ringle dot org>]

Michael Snyder wrote:
> On Tue, 2007-03-06 at 09:31 -0500, Jon Ringle wrote:
>   
> > When I use a native gdb-6.6 on the uclibc target, I don't see any 
> > SIGUSR1 signals being intercepted by gdb (so I don't have to do 'handle 
> > SIGUSR1 nostop noprint') and I see correct behaviour using 'next'.
> >     
The above comment about SIGUSR1 is incorrect. When I ran the test, I was 
actually using SIGALRM which is why I didn't see any SIGUSR1 events... 
sorry for the confusion there.
> Important question -- does gdb thread support (either native or
> remote/gdbserver) work at all with uclibc?
Yes, thread support seems to work just fine from both native gdb and 
gdbserver <-> crossgdb scenarios. "info threads" shows me a list of 
threads and I can use the "thread" command to switch thread contexts and 
see a backtrace of each thread.

Jon