From: Doug Evans <dje@google.com>
To: Sterling Augustine <saugustine@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Script to compare pubnames, gdb index as produced by gold and gdb index as produced by gdb
Date: Fri, 27 Apr 2012 02:06:00 -0000 [thread overview]
Message-ID: <CADPb22RZ0zb6dF6vGH=RhEgEFeg3YuA7txcfWGcBUP0XSnODvA@mail.gmail.com> (raw)
In-Reply-To: <CAEG7qUysAyUao1-Y_hBYA_tpiQ4cuFhVEDuO4jE1bb3nvpJYFQ@mail.gmail.com>
On Thu, Apr 26, 2012 at 4:40 PM, Sterling Augustine
<saugustine@google.com> wrote:
> Enclosed is patch with a python script which takes a binary and
> performs a three-way comparison between the elements in:
>
> 1. The pubnames and pubtypes sections as generated by gcc
> 2. The .gdb_index section as generated by gold
> 3. The .gdb_index section as generated by gdb
>
> I have found it very useful in working on the fission project and I
> suspect anyone else who is working on gdb_index would also find it
> useful. I'm very open to moving it to a different location--is there
> no "contrib" directory?--or not checking it in at all.
>
> In a perfect world, this script would be included in the testsuite and
> run against a wide variety of programs, but the configury associated
> with determining whether the right versions of gdb, gold and gcc are
> available is beyond my ken.
There is/was a src/contrib directory, but setting aside a possibility
of separating gdb and binutils trees src/contrib would be shared by a
lot of packages.
Since we have a few outstanding requests for where to put similar things,
I propose creating src/gdb/contrib.
>
> Thanks,
>
> Sterling
>
>
> 012-04-26 Sterling Augustine <saugustine@google.com>
>
> * test_pubnames_and_indexes.py: New file.
next prev parent reply other threads:[~2012-04-27 0:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 0:37 Sterling Augustine
2012-04-27 2:06 ` Doug Evans [this message]
2012-04-27 16:01 ` Tom Tromey
2012-04-27 18:48 ` Doug Evans
2012-04-27 19:44 ` Joel Brobecker
2012-04-27 20:17 ` Tom Tromey
2012-04-30 18:43 ` Sterling Augustine
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='CADPb22RZ0zb6dF6vGH=RhEgEFeg3YuA7txcfWGcBUP0XSnODvA@mail.gmail.com' \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=saugustine@google.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