From: Daniel Jacobowitz <drow@false.org>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: Pedro Alves <pedro_alves@portugalmail.pt>,
gdb-patches@sourceware.org,
Joel Brobecker <brobecker@adacore.com>
Subject: Re: [commit/AIX] Fix error when loading core file
Date: Mon, 21 May 2007 13:32:00 -0000 [thread overview]
Message-ID: <20070521133216.GC1392@caradoc.them.org> (raw)
In-Reply-To: <200705211324.l4LDOPdZ013445@d12av02.megacenter.de.ibm.com>
On Mon, May 21, 2007 at 03:24:25PM +0200, Ulrich Weigand wrote:
> Another reason why I like the TARGET_OBJECT_LDINFO approach
> is that the ldinfo is also present in core files. Using a
> xfer_partial object allows to cleanly support both native
> and core file debugging (and it can also be extended to
> support remote debugging, if we ever want to do that on AIX).
FWIW, that will work with solib-target too; I didn't use a target
object, but now that you've mentioned it I see that I could have.
I should have thought of that; the needs are very similar.
Of course, if I want to use a target object for this then I need to
change the qfDllInfo packet to a qXfer:libraries:read packet, which
means I can no longer test with my current SymbianOS target - that's
one reason why I've been avoiding cosmetic changes to the protocol.
But that's not a showstopper.
What do you think - would the centralized bookkeeping be helpful,
even though you don't have explicit load and unload reports?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-05-21 13:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-20 0:01 Joel Brobecker
2007-05-20 15:12 ` Ulrich Weigand
2007-05-20 15:50 ` Pedro Alves
2007-05-20 23:22 ` Pedro Alves
2007-05-21 13:24 ` Ulrich Weigand
2007-05-21 13:32 ` Daniel Jacobowitz [this message]
2007-05-28 20:00 ` Ulrich Weigand
2007-05-28 20:52 ` Daniel Jacobowitz
2007-05-31 21:24 ` Ulrich Weigand
2007-05-31 21:43 ` Daniel Jacobowitz
2007-05-22 18:14 ` Joel Brobecker
2007-05-22 23:19 ` Joel Brobecker
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=20070521133216.GC1392@caradoc.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro_alves@portugalmail.pt \
--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