public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Efim Monjak <ymonyak@lipowsky.de>
Cc: gdb@sources.redhat.com
Subject: Re: break of time loop
Date: Thu, 27 Oct 2005 14:34:00 -0000	[thread overview]
Message-ID: <20051027143417.GA23869@nevyn.them.org> (raw)
In-Reply-To: <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

  reply	other threads:[~2005-10-27 14:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-27 14:04 Efim Monjak
2005-10-27 14:34 ` Daniel Jacobowitz [this message]
2005-10-27 15:19 Efim Monjak
2005-10-27 15:23 ` Daniel Jacobowitz
2005-10-27 15:47 Efim Monjak
2005-10-27 18:08 ` Daniel Jacobowitz
2005-10-31 13:56 Efim Monjak
2005-10-31 14:19 ` Daniel Jacobowitz
2005-11-03 10:42 Efim Monjak
2005-11-03 21:23 ` Daniel Jacobowitz
2005-11-04 10:52 Efim Monjak

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20051027143417.GA23869@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb@sources.redhat.com \
    --cc=ymonyak@lipowsky.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).