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: Mon, 15 Dec 2008 13:22:00 -0000 [thread overview]
Message-ID: <52D34F10-34A0-4611-938F-FF8CCB2F24CC@adacore.com> (raw)
In-Reply-To: <200812141737.mBEHbukM021475@d12av02.megacenter.de.ibm.com>
On Dec 14, 2008, at 6:37 PM, Ulrich Weigand wrote:
> The following patch combines the ops->bfd_open callback I need for
> the Cell debugger with the OBJF_KEEPBFD, and also extracts the bulk
> of the solib_bfd_open functionality into subroutines that might be
> re-used by target-specific implementations.
>
> Can you verify that this would also allow a Darwin implementation?
Hi Ulrich,
yes this patch also allows a Darwin implementation. I also think that
this
approach is better than mine as it is more generic and is smaller.
I would be very happy if it were integrated.
Just a side comment on your patch:
> diff -urNp gdb-orig/gdb/objfiles.c gdb-head/gdb/objfiles.c
> --- gdb-orig/gdb/objfiles.c 2008-12-06 20:28:59.000000000 +0100
> +++ gdb-head/gdb/objfiles.c 2008-12-14 17:52:16.000000000 +0100
> @@ -424,7 +424,7 @@ free_objfile (struct objfile *objfile)
>
> /* We always close the bfd. */
>
> - if (objfile->obfd != NULL)
> + if (objfile->obfd != NULL && !(objfile->flags & OBJF_KEEPBFD))
Humm, the above comment is not true anymore!
Thank you,
Tristan.
next prev parent reply other threads:[~2008-12-15 13:22 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
2008-12-11 13:12 ` Tristan Gingold
2008-12-14 17:40 ` Ulrich Weigand
2008-12-15 13:22 ` Tristan Gingold [this message]
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=52D34F10-34A0-4611-938F-FF8CCB2F24CC@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