Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tristan Gingold <gingold@adacore.com>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] solib for darwin
Date: Thu, 04 Dec 2008 16:01:00 -0000	[thread overview]
Message-ID: <02D4698D-539F-4A69-A72A-50941F3F0C99@adacore.com> (raw)
In-Reply-To: <200812041538.mB4FcQsB007133@d12av02.megacenter.de.ibm.com>


On Dec 4, 2008, at 4:38 PM, Ulrich Weigand wrote:

> Interesting; I've been running into the same problem with supporting
> SPU contexts as libraries in the context of the multi-architecture
> Cell debugger.

Fun!  We have common interest to improve the multi-arch support in gdb.

> However, instead of just overriding the bfd_check_format call (which
> b.t.w. does a lot more than just checking the format, no matter its
> name :-/), I've allowed the solib implementation to override the
> whole solib_bfd_open call; this seems to provide more options for
> future changes ...

Right, your approach is more generic that mine.  However with your  
approach,
we need to also create a more generic version of solib_bfd_open so  
that the
overriders don't have to duplicate all the features of the current  
solib_bfd_open
(handling remotes, pathes...)

I think that with your patch I don't need anymore to change non-Darwin  
files.

> I've been wondering about the two bfds as well; note that solib simply
> mirrors what is being done for the main executable file (where we have
> one bfd for the exec file and one for the symbol file).  With my
> patch I've kept two bfds, but call the solib override implementation
> to open each of them.

My concern was speed and memory resources as the number of shared  
libraries might be
large and access to them are slower (search path, ...)
Anyway, this can be addressed later.

> Maybe you can have a look at my patch:
> http://sourceware.org/ml/gdb-patches/2008-09/msg00136.html
> and see whether this would solve your problem as well (or if we can
> come up with a joint approach to solve both problems).

I think it does.  Do you plan to commit it ?

Thanks,
Tristan.


  reply	other threads:[~2008-12-04 16:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-03 12:55 Tristan Gingold
2008-12-04 15:39 ` Ulrich Weigand
2008-12-04 16:01   ` Tristan Gingold [this message]
2008-12-11 13:12   ` Tristan Gingold
2008-12-14 17:40     ` Ulrich Weigand
2008-12-15 13:22       ` Tristan Gingold
2008-12-17 19:46         ` [rfc] Allow platform-specific override for solib_bfd_open (Re: [RFC] solib for darwin) Ulrich Weigand
2009-01-15 16:37           ` Ulrich Weigand
2009-01-15 16:53             ` Tristan Gingold

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=02D4698D-539F-4A69-A72A-50941F3F0C99@adacore.com \
    --to=gingold@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=uweigand@de.ibm.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