Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Remove ignoring leading exec events code.
Date: Fri, 14 Mar 2008 18:06:00 -0000	[thread overview]
Message-ID: <20080314180611.GB31663@caradoc.them.org> (raw)
In-Reply-To: <200803141212.31845.vladimir@codesourcery.com>

On Fri, Mar 14, 2008 at 12:12:31PM +0300, Vladimir Prus wrote:
> 
> GDB has some code to handle a case where target reports more
> that one exec event when execing. However, it turns out that
> all target say that exactly one event is reported, and 
> therefore that code is of no use. The comments for that code
> is dated 2002-12-05 and mentions HP-UX, which I presume had this
> bug fixed. Even if some new target appears with the same bug,
> as the comment say, it's better to handle this in target_wait,
> not in the generic infrun code.
> 
> OK?

OK.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-03-14 18:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-14  9:12 Vladimir Prus
2008-03-14 18:06 ` Daniel Jacobowitz [this message]
2008-03-17 18:28   ` Michael Snyder

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=20080314180611.GB31663@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=vladimir@codesourcery.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