From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Handle 64-bit Solaris/x86 ld.so.1
Date: Wed, 19 Sep 2018 09:11:00 -0000 [thread overview]
Message-ID: <yddefdpn97k.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <20180917183723.GF19172@adacore.com> (Joel Brobecker's message of "Mon, 17 Sep 2018 11:37:23 -0700")
Hi Joel,
> Hello Rainer,
>
>> 2018-06-27 Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
>>
>> * solib-svr4.c (svr4_same_1): Also handle amd64 ld.so.1.
>
> Looks good to me. OK to push, but trying to have the correct
> author in the ChangeLog file.
this proved to be a bit more difficult this time:
* The earliest trace in the solaris-userland repo is for the import of
gdb 6.8 by George Vasick (gdb.solib-svr4.patch), at which point the
patch contained both amd64 and sparcv9 parts.
The sparcv9 part was committed (independently discovered, I suppose)
by yourself:
https://sourceware.org/ml/gdb-patches/2008-02/msg00026.html
* However, the gdb 6.8 part goes back to the OpenSolaris sfw repo, which
to the best of my knowledge has never been available outside of Sun.
I happend to have some old tarballs of the sources around, though,
where the patch is present in sfw-src-b147-20100818.tar.bz2 (still gdb
6.8), but missing in the earlier sfw-src-b101a-20081022.tar.bz2 (gdb
6.3).
* Information from my contacts within Oracle seems to confirm George's
authorship, so this seems to be the best we can do here.
I believe that's enough software archaeology for today ;-)
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
prev parent reply other threads:[~2018-09-19 9:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-17 14:24 Rainer Orth
2018-09-17 18:37 ` Joel Brobecker
2018-09-19 9:11 ` Rainer Orth [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=yddefdpn97k.fsf@CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).