Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: "Ulrich Weigand" <uweigand@de.ibm.com>,  drow@false.org
Subject: Re: [patch, rfc] Re: target_find_description question
Date: Fri, 05 Sep 2008 13:11:00 -0000	[thread overview]
Message-ID: <200809051411.11686.pedro@codesourcery.com> (raw)
In-Reply-To: <200809042359.m84NxTYO018519@d12av02.megacenter.de.ibm.com>

On Friday 05 September 2008 00:59:29, Ulrich Weigand wrote:

> In addition, this has some further benefits:
> - We can now properly handle cases where the inferior dies while in the
>   shell (the FIXME in the old startup_inferior code)
> - The treat_exec_as_sigtrap argument to handle_inferior_event is no longer
>   used and could be removed (not part of this patch)

Of course, a specific stop_soon flag for startup/going through the shell
would also make it possible to do this in handle_inferior_event, but indeed,
it would be more complicated.  

> Tested on amd64-linux with no regressions.
>
> What do you think?

I like it.

Notice that there are fork-child targets that handle this even
at a lower level, within target_wait (see gnu-nat.c).

-- 
Pedro Alves


  parent reply	other threads:[~2008-09-05 13:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-02 23:49 Ulrich Weigand
2008-09-04 12:12 ` Daniel Jacobowitz
2008-09-04 19:17   ` Ulrich Weigand
2008-09-04 21:52     ` Daniel Jacobowitz
2008-09-04 22:12       ` Pedro Alves
2008-09-04 22:27         ` Pedro Alves
2008-09-05  0:00           ` [patch, rfc] " Ulrich Weigand
2008-09-05  2:40             ` Daniel Jacobowitz
2008-09-05 13:11             ` Pedro Alves [this message]
2008-09-06  1:55             ` Joel Brobecker
2008-09-11 16:13             ` Ulrich Weigand

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=200809051411.11686.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=uweigand@de.ibm.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