From: "Newman, Mark (N-Superior Technical Resource Inc)" <mark.newman@lmco.com>
To: "Newman,
Mark (N-Superior Technical Resource Inc)" <mark.newman@lmco.com>,
gdb@sources.redhat.com
Subject: RE: async operation
Date: Mon, 17 Nov 2003 17:30:00 -0000 [thread overview]
Message-ID: <F56FBA314E8E5A41895F0DA8F6716A6D02A56A@EMSS04M11.us.lmco.com> (raw)
No response on this - so I am going to change GDB so that it will correctly handle an "interrupt" command to stop the inferior when in async mode.
I will put the final changes in as patches and as a bug report unless someone objects.
Mark Newman
> -----Original Message-----
> From: gdb-owner@sources.redhat.com
> [mailto:gdb-owner@sources.redhat.com]On Behalf Of Newman, Mark
> (N-Superior Technical Resource Inc)
> Sent: Friday, November 14, 2003 2:30 PM
> To: gdb@sources.redhat.com
> Subject: async operation
>
>
>
> Is there anyway to cleanly stop a remote target manually when
> in async mode.
>
> I tried using the "stop" command which makes it through the
> async filtering in top.c - however stop simply says it is not
> a valid command. There is logic in here for cleanly stopping
> when a break occurs (?) but I can't find any to allow the
> operator to stop the target?
>
> I add'ed "interrupt" to the filtering but it does not clear
> the target_executing flag.
>
>
> Mark Newman
>
next reply other threads:[~2003-11-17 17:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-17 17:30 Newman, Mark (N-Superior Technical Resource Inc) [this message]
2003-11-18 3:56 ` Andrew Cagney
2003-11-18 5:33 ` Mark Newman
2003-11-18 7:12 ` Daniel Jacobowitz
2003-11-18 14:57 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2003-11-25 16:07 Newman, Mark (N-Superior Technical Resource Inc)
2003-11-18 15:50 Newman, Mark (N-Superior Technical Resource Inc)
2003-11-18 15:55 ` Daniel Jacobowitz
2003-12-04 21:01 ` Elena Zannoni
2003-12-04 22:09 ` Mark Newman
2003-11-14 19:30 Newman, Mark (N-Superior Technical Resource Inc)
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=F56FBA314E8E5A41895F0DA8F6716A6D02A56A@EMSS04M11.us.lmco.com \
--to=mark.newman@lmco.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