From: Pedro Alves <pedro@codesourcery.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Share the shared library list between inferiors
Date: Mon, 03 Nov 2008 15:05:00 -0000 [thread overview]
Message-ID: <200811031504.38355.pedro@codesourcery.com> (raw)
In-Reply-To: <20081103142920.GA28482@caradoc.them.org>
On Monday 03 November 2008 14:29:20, Daniel Jacobowitz wrote:
> On Mon, Oct 27, 2008 at 11:29:04PM +0000, Pedro Alves wrote:
> > There are several ways to skin this cat. This one seemed like
> > the smallest, most extensible and malleable one from GDB's side, because
> > it doesn't cast to stone any new protocol extension --- which may
> > prove limited to some systems (some memory regions shared, others not;
> > some shared but visible at different addresses in different
> > inferiors/cores, etc.). I was hoping we'd cross that bridge when
> > we start seeing those systems reporting multi process support
> > to GDB.
> >
> > What do people think about this?
>
> I have one request. Could you expand the comment to mention the other
> properties you're associating with this flag?
>
> Global breakpoints and a single common target description don't
> obviously follow from "global shared library list".
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).
--
Pedro Alves
next prev parent reply other threads:[~2008-11-03 15:05 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 [this message]
2008-11-03 15:13 ` Daniel Jacobowitz
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=200811031504.38355.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
/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