From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: pedro_alves@portugalmail.pt (Pedro Alves)
Cc: gdb-patches@sourceware.org, brobecker@adacore.com (Joel Brobecker)
Subject: Re: [commit/AIX] Fix error when loading core file
Date: Mon, 21 May 2007 13:24:00 -0000 [thread overview]
Message-ID: <200705211324.l4LDOPdZ013445@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <4650B245.3060306@portugalmail.pt> from "Pedro Alves" at May 20, 2007 09:40:37 PM
Pedro Alves wrote:
> Pedro Alves wrote:
> > Ulrich Weigand wrote:
> >>
> >> I'd thought of defining a TARGET_OBJECT_LDINFO xfer_partial object
> >> that reflects the contents of the ldinfo, and use this in the
> >> implementation of a (platform-independent) solib-aix.c file.
> >> The rs6000 native target and the core file support would need to
> >> be extended to supply that object.
> >>
> >
> > If AIX needs to use native calls to get at the shared libraries list,
> > perhaps you could also look if the solib-target.c Daniel is pushing
> > for remote dll support, and see if it would be a good fit for AIX too.
> > As a quick look it seems so. You would move aix_current_sos
> > to the target_ops, and perhaps needs a few other tweaks
> > (aix_in_dynsym_resolve_code, and aix_solib_create_inferior_hook).
> > Although he presented it as remote support, it also makes sense
> > for native win32 debugging, so it may also make sense as native
> > AIX debugging.
> >
>
> Hummm, looking at it for another 30 seconds, made me realize
> it isn't fit. Although AIX tells us something loaded with
> 'wait (&status), (status == 0x57c)', it doesn't tell us
> specifically *what* was loaded - we have to build a list
> of current_sos every time. Being so, case solib-target.c
> gets more in the way than helps. Your approach seems best.
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).
In any case, thanks for looking at this!
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2007-05-21 13:24 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 [this message]
2007-05-21 13:32 ` Daniel Jacobowitz
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=200705211324.l4LDOPdZ013445@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro_alves@portugalmail.pt \
/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