From: Andrew Cagney <cagney@gnu.org>
To: Randolph Chung <randolph@tausq.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Assume solib.h
Date: Sat, 13 Nov 2004 01:10:00 -0000 [thread overview]
Message-ID: <41955E85.50104@gnu.org> (raw)
In-Reply-To: <20041112011141.GY15714@tausq.org>
Randolph Chung wrote:
>>There's just one non-technical nit.
>>
>>It means breaking non solib.[hc] shared library systems. Kevin
>>indicated that there were two - AIX and HP/UX remaining. I think we can
>>live with that - we've patiently waited for what, more than two years
>>for nothing to happen, so it is now time to give things that gentle pus
>
>
> I'm not prepared to sign up for hpux support, but can you explain some
> more what will break and what is needed to fix it? Despite the lack of
> maintainence, there are still a good number of people out there using
> gdb on hpux (judging by private mail I've received since I started
> working on hppa-linux support)....
Have a look at solist.h which contains:
> struct target_so_ops
> {
> /* Adjust the section binding addresses by the base address at
> which the object was actually mapped. */
> void (*relocate_section_addresses) (struct so_list *so,
> struct section_table *);
...
it just needs to implement that object (see solib-svr4.c). Without it,
shared libraries wouldn't work but everything else should.
We need to find a way of flushing some of these people still using GDB
on HP/UX (or are they using HP's WDB fork?) and, unfortunate as it is,
push-come-to-shove is one of the most effective ways of doing this.
Anyway, HP/UX has a more immediate problem - it's still using
deprecated_registers[] and that's now past its end-of-life :-/
Andrew
prev parent reply other threads:[~2004-11-13 1:10 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-11 19:39 Andrew Cagney
2004-11-11 20:06 ` Mark Kettenis
2004-11-11 21:48 ` Andrew Cagney
2004-11-11 22:24 ` Mark Kettenis
2004-11-12 15:52 ` Andrew Cagney
2004-11-12 17:20 ` Eli Zaretskii
2004-11-15 21:32 ` Kevin Buettner
2004-11-15 23:35 ` Mark Kettenis
2004-11-17 17:35 ` Eli Zaretskii
2004-11-15 23:59 ` Andrew Cagney
2004-11-16 1:20 ` Daniel Jacobowitz
2004-11-16 5:00 ` Eli Zaretskii
2004-11-16 8:37 ` Mark Kettenis
2004-11-16 20:54 ` Eli Zaretskii
2004-11-16 16:14 ` Andrew Cagney
2004-11-16 19:18 ` Mark Kettenis
2004-11-18 14:10 ` Andrew Cagney
2004-11-18 14:37 ` Mark Kettenis
2004-11-18 17:28 ` Kevin Buettner
2004-11-19 17:11 ` Andrew Cagney
2004-11-19 17:25 ` Randolph Chung
2004-11-19 17:36 ` Joel Brobecker
2004-11-19 17:40 ` Randolph Chung
2004-11-19 17:56 ` Joel Brobecker
2004-11-19 19:29 ` Joseph S. Myers
2004-11-16 21:06 ` Eli Zaretskii
2004-11-16 22:27 ` Andrew Cagney
2004-11-17 4:52 ` Eli Zaretskii
2004-11-16 1:40 ` Daniel Jacobowitz
2004-11-16 4:54 ` Eli Zaretskii
2004-11-16 16:31 ` Andrew Cagney
2004-11-16 19:45 ` Mark Kettenis
2004-11-16 21:06 ` Eli Zaretskii
2004-11-12 1:11 ` Randolph Chung
2004-11-13 1:10 ` Andrew Cagney [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=41955E85.50104@gnu.org \
--to=cagney@gnu.org \
--cc=gdb-patches@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