This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: break of time loop
- From: Daniel Jacobowitz <drow at false dot org>
- To: Efim Monjak <ymonyak at lipowsky dot de>
- Cc: gdb at sources dot redhat dot com
- Date: Thu, 27 Oct 2005 10:34:17 -0400
- Subject: Re: break of time loop
- References: <4360DE7F.5020504@lipowsky.de>
On Thu, Oct 27, 2005 at 04:04:47PM +0200, Efim Monjak wrote:
> The GDB send in this case to target many "step" commands.
> I try to stop the processing of loop by crtl+c. Target receive
> code 0x03 and responce it with Packet:
> TAAn...:r...;n...:r...;n...:r...;
> there AA ist signal TARGET_SIGNAL_INT = 02.
> I can see the response from target.
> It is possible the ctrl+c is sent after "step" command before
> it is responsed. In this case they are two responsies one after other.
> But GDB don't stops to send "step" commands.
> How must be responsed the ctrl+c?
Sorry, I'm not sure I understand your question. Can you give us a
transcript of the remote protocol session (set debug remote 1) that you
think is wrong?
If GDB sends an interrupt to the remote target, the target should
return a stop response (T packet, above). At that point the target is
stopped. There shouldn't be another response to any pending step
commands.
--
Daniel Jacobowitz
CodeSourcery, LLC