From: Kevin Buettner <kevinb@cygnus.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] solib-svr4.c: Fix set_solib_svr4_fetch_link_map_offsets
Date: Fri, 21 Sep 2001 20:14:00 -0000 [thread overview]
Message-ID: <1010922031340.ZM19859@ocotillo.lan> (raw)
In-Reply-To: <3BABF816.9040308@cygnus.com>
On Sep 21, 10:31pm, Andrew Cagney wrote:
> Instead of having a global variable, have you looked at registering a
> data pointer and then calling set_gdbarch_data(), from
> set_solib_svr4_fetch_link_map_offsets(), to set it?
Well, I thought I had, but now that I look at it again, it does look
like this'll work. I'll give it a try...
> The only potential problem I can see with this is with non- multi-arch
> but there, looking at the code I think it is already handled.
I think you're right.
Kevin
prev parent reply other threads:[~2001-09-21 20:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1010920205607.ZM17368@ocotillo.lan>
[not found] ` <s3ielp1ecwc.fsf@soliton.wins.uva.nl>
2001-09-20 15:16 ` Kevin Buettner
2001-09-21 18:56 ` Andrew Cagney
2001-09-21 20:31 ` Kevin Buettner
2001-09-21 20:42 ` Andrew Cagney
2001-09-21 19:32 ` Andrew Cagney
2001-09-21 20:14 ` Kevin Buettner [this message]
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=1010922031340.ZM19859@ocotillo.lan \
--to=kevinb@cygnus.com \
--cc=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.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