Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
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:21:00 -0000	[thread overview]
Message-ID: <20080806142017.GA27139@caradoc.them.org> (raw)
In-Reply-To: <20080805221125.A7C2F4E4A@hiauly1.hia.nrc.ca>

On Tue, Aug 05, 2008 at 06:11:24PM -0400, John David Anglin wrote:
> The change below fixes the problem referred to in the NEWS file regarding
> the hppa64-hp-hpux11* target.  The problem was a NULL load map pointer was
> being passed in the dlgetmodinfo and dlgetname calls.  This was causing
> pa64_target_read_memory() to return 0, and as a result the dlgetmodinfo
> call was failing.
> 
> It's not entirely clear why the code to find the load map was failing
> but I believe it is because the dynamic loader had not initialized the
> map at the time the call to find the map was made.
> 
> As described here <http://docs.hp.com/en/B2355-60130/dlmodinfo.3C.html>,
> it is not necessary to supply a memory read function for the calls to
> dlgetmodinfo and dlgetname.  This causes the dynamic loader to use its
> own data structures to find the correct module.
> 
> Getting rid of the code to find the load map results in some simplification.
> 
> Please install if ok.

Does this really do what you want it to?

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.

-- 
Daniel Jacobowitz
CodeSourcery


  parent reply	other threads:[~2008-08-06 14:21 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 [this message]
2008-08-06 14:59   ` John David Anglin
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=20080806142017.GA27139@caradoc.them.org \
    --to=drow@false.org \
    --cc=dave@hiauly1.hia.nrc.ca \
    --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