From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
To: drow@false.org (Daniel Jacobowitz)
Cc: gdb-patches@sourceware.org, randolph@tausq.org
Subject: Re: [patch] Fixed shared library handling in solib-pa64.c
Date: Wed, 06 Aug 2008 14:59:00 -0000 [thread overview]
Message-ID: <20080806145833.3A3CA4E87@hiauly1.hia.nrc.ca> (raw)
In-Reply-To: <20080806142017.GA27139@caradoc.them.org> from "Daniel Jacobowitz" at Aug 6, 2008 10:20:17 am
> Looking at that HP man page, it looks like dlmodinfo will use "its own
> data structures" - i.e. GDB's load map, not the debugged program's.
You are correct. I was confused by testing on gdb itself. However,
the part to get the info about the dynamic loader may be ok.
Dave
--
J. David Anglin dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada (613) 990-0752 (FAX: 952-6602)
next prev parent reply other threads:[~2008-08-06 14:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-05 22:12 John David Anglin
2008-08-06 13:06 ` Randolph Chung
2008-08-06 14:21 ` Daniel Jacobowitz
2008-08-06 14:59 ` John David Anglin [this message]
2008-08-06 18:20 ` [patch] Fix shared library handling in solib-pa64.c (take 2) John David Anglin
2008-08-06 19:26 ` Daniel Jacobowitz
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=20080806145833.3A3CA4E87@hiauly1.hia.nrc.ca \
--to=dave@hiauly1.hia.nrc.ca \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=randolph@tausq.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