Daniel Jacobowitz wrote:
> On Mon, Mar 05, 2007 at 03:05:34PM -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 haven't seen this problem before.  Can you make a small test case
> which demonstrates the problem, maybe?
>
>   
Attached is a test case. <cid:part1.03040401.03010207@ringle.org>
> What target are you using?
>
>   
My target is armeb-linux.

Thanks,

Jon