Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: "Newman,
	Mark (N-Superior Technical Resource Inc)" <mark.newman@lmco.com>
Cc: gdb@sources.redhat.com
Subject: Re: async operation
Date: Tue, 18 Nov 2003 03:56:00 -0000	[thread overview]
Message-ID: <3FB9986F.2030405@gnu.org> (raw)
In-Reply-To: <F56FBA314E8E5A41895F0DA8F6716A6D02A56A@EMSS04M11.us.lmco.com>

> 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.

Well you did post on a Saturday ;-)

> 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 think the description for "stop" explains why that does nothing:

   if (!dbx_commands)
     stop_command =
       add_cmd ("stop", class_obscure, not_just_help_class_command, 
"There is no
`stop' command, but you can set a hook on `stop'.\n\
This allows you to set a list of commands to be run each time execution\n\
of the program stops.", &cmdlist);

> I add'ed "interrupt" to the filtering but it does not clear the target_executing flag.

You should see "fetch_inferior_event" clear that flag after it's 
received notification that the target really has stopped.

Andrew



  reply	other threads:[~2003-11-18  3:56 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)
2003-11-18  3:56 ` Andrew Cagney [this message]
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=3FB9986F.2030405@gnu.org \
    --to=cagney@gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=mark.newman@lmco.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