From: Tom Tromey <tromey@redhat.com>
To: Panu Matilainen <pmatilai@redhat.com>
Cc: Roland McGrath <roland@redhat.com>,
Project Archer <archer@sourceware.org>
Subject: Re: find-debuginfo.sh change for gdb index
Date: Tue, 06 Jul 2010 18:35:00 -0000 [thread overview]
Message-ID: <m38w5ocvcj.fsf@fleche.redhat.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1007051223290.8757@localhost> (Panu Matilainen's message of "Mon, 5 Jul 2010 12:36:32 +0300 (EEST)")
>>>>> "Panu" == Panu Matilainen <pmatilai@redhat.com> writes:
Panu> So it would be this patch, right?
Yes.
Panu> Is the necessary patch(es) already in rawhide gdb, I dont see anything
Panu> obviously related in gdb changelogs?
Yeah, it is still under discussion upstream.
One thing that came up is that the current approach of using file
size+mtime to determine whether the index is valid is not super.
Two competing ideas:
1. Put the build-id into the index file, then verify it.
2. Require the index to be a section in the ELF object.
This has the nice property that no validation need be done.
However, it would require a further tweak to find-debuginfo.sh.
Any comments?
I would like to resolve this ASAP.
Tom
next prev parent reply other threads:[~2010-07-06 18:35 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-29 22:32 Tom Tromey
2010-06-29 23:21 ` Roland McGrath
2010-06-30 17:35 ` Tom Tromey
2010-06-30 18:14 ` Roland McGrath
2010-06-30 18:23 ` Tom Tromey
2010-06-30 20:42 ` Tom Tromey
2010-06-30 20:44 ` Roland McGrath
2010-06-30 21:25 ` Tom Tromey
2010-06-30 21:58 ` Tom Tromey
2010-06-30 22:00 ` Tom Tromey
2010-06-30 22:14 ` Roland McGrath
2010-07-02 19:55 ` Tom Tromey
2010-07-05 9:36 ` Panu Matilainen
2010-07-05 9:48 ` Jan Kratochvil
2010-07-05 10:39 ` Panu Matilainen
2010-07-06 18:35 ` Tom Tromey [this message]
2010-07-06 19:14 ` Roland McGrath
2010-07-06 19:41 ` Tom Tromey
2010-07-06 20:28 ` Roland McGrath
2010-07-08 15:56 ` Tom Tromey
2010-07-08 20:36 ` Tom Tromey
2010-07-08 22:53 ` Roland McGrath
2010-07-09 5:07 ` Panu Matilainen
2010-07-09 17:48 ` Tom Tromey
2010-07-30 21:36 ` Tom Tromey
2010-07-30 23:07 ` Roland McGrath
2010-07-30 23:09 ` Jan Kratochvil
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=m38w5ocvcj.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=archer@sourceware.org \
--cc=pmatilai@redhat.com \
--cc=roland@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).