This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: [SPAM] Re: gdbserver signals interfere with {next,step{,i}}
Daniel Jacobowitz wrote:
On Mon, Mar 05, 2007 at 09:24:30PM -0500, Jon Ringle wrote:
My target uses uclibc-0.9.28 rather than a glibc libc. Could that be a
factor here?
Yes, it certainly could be.
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'. What
would gdbserver-6.6 be doing different that a native gdb-6.6 in regards
to signal handling?
Jon
- References:
- gdbserver signals interfere with {next,step{,i}}
- Re: gdbserver signals interfere with {next,step{,i}}
- Re: gdbserver signals interfere with {next,step{,i}}
- Re: gdbserver signals interfere with {next,step{,i}}
- Re: [SPAM] Re: gdbserver signals interfere with {next,step{,i}}
- Re: gdbserver signals interfere with {next,step{,i}}
- Re: [SPAM] Re: gdbserver signals interfere with {next,step{,i}}
- Re: [SPAM] Re: gdbserver signals interfere with {next,step{,i}}