From: Michael Snyder <msnyder@specifix.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Vladimir Prus <vladimir@codesourcery.com>,
gdb-patches@sources.redhat.com
Subject: Re: [RFA] Remove ignoring leading exec events code.
Date: Mon, 17 Mar 2008 18:28:00 -0000 [thread overview]
Message-ID: <1205778508.19253.948.camel@localhost.localdomain> (raw)
In-Reply-To: <20080314180611.GB31663@caradoc.them.org>
On Fri, 2008-03-14 at 14:06 -0400, Daniel Jacobowitz wrote:
> 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.
Hmm, just a cautionary note. The code / practice that you're
talking about stretches WAAAAY back in history. I'm pretty
sure it was not only for HP-UX. There may be other (possibly
historical) targets that depend on this.
I can remember that code being there (and being necessary)
in the mid-1990's. I don't necessarily remember on what
targets it came into play, but I might guess that SunOS
(perhaps solaris or perhaps before) was one of them.
prev parent reply other threads:[~2008-03-17 18:28 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
2008-03-17 18:28 ` Michael Snyder [this message]
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=1205778508.19253.948.camel@localhost.localdomain \
--to=msnyder@specifix.com \
--cc=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