From: Daniel Jacobowitz <drow@false.org>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Share the shared library list between inferiors
Date: Mon, 03 Nov 2008 15:13:00 -0000 [thread overview]
Message-ID: <20081103151302.GA31147@caradoc.them.org> (raw)
In-Reply-To: <200811031504.38355.pedro@codesourcery.com>
On Mon, Nov 03, 2008 at 03:04:38PM +0000, Pedro Alves wrote:
> Certainly! Sorry about that. That came from the fact that feature
> implementation having had several dressings over time, and I guess
> I had just started seeing through the name.
>
> I could also rename the gdbarch method to something like
> gdbarch_code_is_shared_between_processes, if you'd like (although
> it sounds a bit long of a name).
I think the name is fine - if we need some day to separate these
features, then we'll create extra gdbarch knobs for them.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-11-03 15:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-28 1:28 Pedro Alves
2008-11-03 14:10 ` Pedro Alves
2008-11-03 14:30 ` Daniel Jacobowitz
2008-11-03 15:05 ` Pedro Alves
2008-11-03 15:13 ` Daniel Jacobowitz [this message]
2008-11-03 16:15 ` Pedro Alves
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=20081103151302.GA31147@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@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