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

[Michael Snyder <Michael.Snyder@palmsource.com>]

On Mon, 2007-03-05 at 15:05 -0500, Jon Ringle wrote:
> Hello,
> 
> I have an application that uses SIGUSR1 to receive timer interrupts. 
> I've done 'handle SIGUSR1 nostop noprint' to avoid gdb from stopping on 
> SIGUSR1.
> I've found that when debugging this application using gdbserver, that I 
> can't use next, nexti, step, or stepi. When I use one of these commands, 
> the application usually just continues without stopping at the next 
> line/instruction.
> 
> If I use a native gdb on the target the problem does not occur.
> If I disable my app from generating the SIGUSR1 and use gdbserver, the 
> problem also goes away.
> 
> I am using gdb-6.6 for gdbserver, native gdb and cross gdb.

Is it possible for your app to use a different signal?
SIGUSR1 has been used by glibc in the old linux pthreads
implementation, and gdb (and gdbserver) both have special
handling built into them for that signal.