From: Kevin Buettner <kevinb@redhat.com>
To: gdb@sources.redhat.com
Subject: Re: Interrupting remote targets from GDB
Date: Thu, 17 Nov 2005 19:52:00 -0000 [thread overview]
Message-ID: <20051117125217.0a503b4e@ironwood.lan> (raw)
In-Reply-To: <20051117185056.GA18702@nevyn.them.org>
On Thu, 17 Nov 2005 13:50:56 -0500
Daniel Jacobowitz <drow@false.org> wrote:
> Fine by me; can we also add a word about what to do with interrupts
> when the target is stopped? I believe they should be dropped rather
> than responded to, per conversation on gdb@ earlier this month.
I've added one sentence to the text I posted earlier.
Here's the revised text:
When a program on the remote target is running, GDB may attempt
to interrupt it by sending a `Ctrl-C' or a BREAK, control of which
is specified via GDB's `remotebreak' setting. The precise meaning
of BREAK is defined by the transport mechanism and may, in fact,
be undefined. `Ctrl-C', on the other hand, is defined for all
transport mechanisms and is represented by sending the single byte
0x03. `Ctrl-C' must not be sent as part of a packet as defined in
the "Overview".
Stubs are not required to recognize these interrupt mechanisms and
the precise meaning associated with receipt of the interrupt is
implementation defined. If the stub is successful at interrupting
the running program, it is expected that it will send one of the
`Stop Reply Packets' to GDB as a result of successfully stopping
the program. Interrupts received while the program is stopped will
be discarded.
next prev parent reply other threads:[~2005-11-17 19:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-17 18:20 Kevin Buettner
2005-11-17 18:51 ` Daniel Jacobowitz
2005-11-17 19:14 ` Kevin Buettner
2005-11-17 19:52 ` Kevin Buettner [this message]
2005-11-17 19:46 ` Eli Zaretskii
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=20051117125217.0a503b4e@ironwood.lan \
--to=kevinb@redhat.com \
--cc=gdb@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).