From: Pedro Alves <pedro@codesourcery.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org, dgraham@nortel.com
Subject: Re: RFC: Do not try g-packet-guess algorithm on exited targets
Date: Mon, 24 Nov 2008 19:17:00 -0000 [thread overview]
Message-ID: <200811241458.47326.pedro@codesourcery.com> (raw)
In-Reply-To: <20081124144821.GA27882@caradoc.them.org>
On Monday 24 November 2008 14:48:21, Daniel Jacobowitz wrote:
> Like the attached? It works in my testing and is much nicer.
Yep, looks good.
> I did have a question while looking at this. We call
> wait_for_inferior via start_remote when connecting to an all-stop
> target, but not when connecting to a non-stop target. Does this
> work because non-stop is always async, and we push the stop replies to
> be noticed by the main event loop?
Yes.
--
Pedro Alves
next prev parent reply other threads:[~2008-11-24 14:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-24 13:53 Daniel Jacobowitz
2008-11-24 14:49 ` Pedro Alves
2008-11-24 14:49 ` Daniel Jacobowitz
2008-11-24 19:06 ` Daniel Jacobowitz
2008-11-24 19:17 ` Pedro Alves [this message]
2008-11-24 20:11 ` Daniel Jacobowitz
2008-12-01 22:10 ` Michael Snyder
2008-12-01 22:18 ` Daniel Jacobowitz
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=200811241458.47326.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=dgraham@nortel.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
/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