From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] New (!) BFD target
Date: Thu, 23 Oct 2003 15:43:00 -0000 [thread overview]
Message-ID: <20031023154358.GA6151@nevyn.them.org> (raw)
In-Reply-To: <3F97625F.3060900@gnu.org>
On Thu, Oct 23, 2003 at 01:08:47AM -0400, Andrew Cagney wrote:
> >Also, how does this interact with the "exec" target, whose
> >functionality it seems to duplicate in some ways? There should be an
> >exec target down the stack somewhere, why aren't you using that?
>
> bfd-target.h is "new" and "re-entrant". "exec.c" is "old" and "very
> very non-re-entrant". Recall that I wrote:
>
> >What you're casually dismissing as trivial: "Not everywhere will need to
> >be converted" and "Eventually, with low urgency, the non-ops should be
> >moved out of it" are exactly the things I also need *now*.
>
> The change I posted, for svr4-solib.o, requires two active bfd-backed
> targets (the executable and ld.so), and hence re-entrency[sp].
>
> Follow on changes can see "corefile.c" and "exec.c" both overhauled to
> use this new bfd-target foundation/parent object.
OK, as commonized code between corefile and exec handling this makes a
bit more sense to me.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-10-23 15:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-23 0:50 Andrew Cagney
2003-10-23 2:41 ` Daniel Jacobowitz
2003-10-23 5:08 ` Andrew Cagney
2003-10-23 15:43 ` Daniel Jacobowitz [this message]
2003-10-31 19:23 ` Andrew Cagney
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=20031023154358.GA6151@nevyn.them.org \
--to=drow@mvista.com \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.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