From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
To: randolph@tausq.org
Cc: gdb@sources.redhat.com
Subject: Re: pc_requires_run_before_use
Date: Wed, 24 Nov 2004 03:55:00 -0000 [thread overview]
Message-ID: <200411240344.iAO3iGm7008085@hiauly1.hia.nrc.ca> (raw)
In-Reply-To: <20041123212126.GR9148@tausq.org> from "Randolph Chung" at Nov 23, 2004 04:21:26 pm
> Does anybody understand what this comment means or what this code is
> supposed to do?
>
> hppa_pc_requires_run_before_use() in hppa-tdep.a says:
I haven't looked at this but I think this is typical of the plabel
setup for lazy binding. In GCC under linux, we need to call into
the dynamic linker to force resolution of the function when doing
function pointer comparisons. This is the infamous __cffc routine.
I think gdb will have similar issues when trying to set a break
in a shared library.
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:[~2004-11-24 3:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 21:43 pc_requires_run_before_use Randolph Chung
2004-11-24 3:55 ` John David Anglin [this message]
2004-11-24 6:47 ` pc_requires_run_before_use Randolph Chung
2004-12-04 0:38 ` pc_requires_run_before_use Randolph Chung
2004-12-04 1:01 ` pc_requires_run_before_use John David Anglin
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=200411240344.iAO3iGm7008085@hiauly1.hia.nrc.ca \
--to=dave@hiauly1.hia.nrc.ca \
--cc=gdb@sources.redhat.com \
--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