From: Eli Zaretskii <eliz@gnu.org>
To: Steven Johnson <sjohnson@sakuraindustries.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa/doc] Add section on interrupts to remote protocol documentation
Date: Fri, 18 Nov 2005 13:53:00 -0000 [thread overview]
Message-ID: <uzmo23xaj.fsf@gnu.org> (raw)
In-Reply-To: <437D60FA.4020506@sakuraindustries.com> (message from Steven Johnson on Fri, 18 Nov 2005 16:04:58 +1100)
> Date: Fri, 18 Nov 2005 16:04:58 +1100
> From: Steven Johnson <sjohnson@sakuraindustries.com>
>
> Otherwise, ^C is ignored as a special character. What does "interrupt"
> mean when you are not doing anything that can be interrupted?
>
> If you are executing code, then you are in the "Dead space" between the
> packet from GDB to the target to get the target to execute code, and the
> reply from that packet. I would have thought during this time, and this
> time only ^C has any relevance? If so then, it doesnt need to be
> quoted, As you cant send a packet during this time.
>
> I think it would be better to say that during this time, and this time
> only is when ^C is relevant, and if received at any other time it is
> processed like that character would be in the message stream.
Isn't this what Kevin's text says? Here's the relevant fragment:
Interrupts received while the program is stopped will be discarded.
next prev parent reply other threads:[~2005-11-18 13:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-18 5:59 Kevin Buettner
2005-11-18 8:35 ` Jim Blandy
2005-11-18 11:20 ` Steven Johnson
2005-11-18 11:57 ` Jim Blandy
2005-11-18 17:23 ` Kevin Buettner
2005-11-18 20:25 ` Jim Blandy
2005-11-18 13:53 ` Eli Zaretskii [this message]
2005-11-18 15:33 ` Steven Johnson
2005-11-18 14:06 ` Eli Zaretskii
2005-11-18 21:45 ` Kevin Buettner
2005-11-18 21:47 ` Daniel Jacobowitz
2005-11-18 22:07 ` Jim Blandy
2005-11-19 10:57 ` Steven Johnson
2005-11-18 22:18 ` Kevin Buettner
2005-11-18 22:19 ` Michael Snyder
2005-11-18 22:38 ` Eli Zaretskii
2005-11-19 1:21 ` Kevin Buettner
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=uzmo23xaj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=sjohnson@sakuraindustries.com \
/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