Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org, Aleksandar Ristovski <ARistovski@qnx.com>
Subject: Re: [PATCH v5 8/8] Tests for validate symbol file using build-id
Date: Tue, 20 May 2014 15:29:00 -0000	[thread overview]
Message-ID: <20140520152934.GA27766@host2.jankratochvil.net> (raw)
In-Reply-To: <87ha4kts54.fsf@fleche.redhat.com>

On Tue, 20 May 2014 16:57:11 +0200, Tom Tromey wrote:
> >>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
> 
> Jan> 2014-02-26  Aleksandar Ristovski  <aristovski@qnx.com
> Jan> 	Tests for validate symbol file using build-id.
> Jan> 	* gdb.server/solib-mismatch-lib.c: New file.
> Jan> 	* gdb.server/solib-mismatch-libmod.c: New file.
> Jan> 	* gdb.server/solib-mismatch.c: New file.
> Jan> 	* gdb.server/solib-mismatch.exp: New file.
> 
> I thought Pedro had wanted these not in gdb.server.
> Or am I confusing that with some other patch?

In a local copy they are moved back to gdb.base/ .
But I haven't re-post the whole series just because of it.
Planning to check it in into gdb.base/ .


> Jan> +if ![is_remote target] {
> Jan> +  untested "only gdbserver supports build-id reporting"
> Jan> +  return -1
> 
> I was mildly confused to read this.
> Isn't build-id also supported natively?

For this case of build-id it is not.  It was discussed in:
	Re: [patchv3 7/8] Validate symbol file using build-id
	Message-ID: <53108EF7.3000708@redhat.com>
	https://sourceware.org/ml/gdb-patches/2014-02/msg00862.html
	https://sourceware.org/ml/gdb-patches/2014-03/msg00011.html


> How does the new functionality interact with the existing build-id
> functionality?

Currently only the separate debug info file is located and validated by
build-id.  This patch is about validating the primary file (without .debug
extension - in fact symbol file as GDB uses that file only for symbols).


Besides all of these there are additional patches:
	http://pkgs.fedoraproject.org/cgit/gdb.git/tree/
	gdb-6.6-buildid-locate-*
which are also about locating the primary files but those patches are for
local (NAT) mode.

Also this series does not validate / locate the main executable, the Fedora
patches above work also for the main executable.

It got all a bit messy so I decided to merge it all and preparing it as an
update (technically add-on) on this patch series.  So also contrary to my
original plans in
	Re: [patchv3 7/8] Validate symbol file using build-id
above I am going to implement the local (NAT) mode for locating the files.
As I expect GDB is not going to unify LocalRemoteFeatureParity soon enough.
It will be about upstreaming the Fedora patchset which is the last largest
Fedora-specific patchsets kept.


Jan


  reply	other threads:[~2014-05-20 15:29 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-19 23:12 [PATCH v5 0/8] Validate binary before use Jan Kratochvil
2014-03-19 22:30 ` [PATCH v5 1/8] Move utility functions to common/ Jan Kratochvil
2014-03-24 20:00   ` Sergio Durigan Junior
2014-05-18 19:05     ` Jan Kratochvil
2014-05-19 18:22       ` Tom Tromey
2014-05-19 22:48         ` Doug Evans
2014-05-19 22:46       ` Doug Evans
2014-05-19 18:21   ` Tom Tromey
2014-03-19 22:31 ` [PATCH v5 5/8] Move linux_find_memory_regions_full & co Jan Kratochvil
2014-05-19 19:19   ` Tom Tromey
2014-03-19 22:31 ` [PATCH v5 4/8] Prepare linux_find_memory_regions_full & co. for move Jan Kratochvil
2014-05-19 19:15   ` Tom Tromey
2014-03-19 22:31 ` [PATCH v5 7/8] Validate symbol file using build-id Jan Kratochvil
2014-03-20  3:51   ` Eli Zaretskii
2014-03-20 13:07     ` Jan Kratochvil
2014-03-20 17:28       ` Eli Zaretskii
2014-03-21 16:58         ` Jan Kratochvil
2014-03-20 13:13   ` Aleksandar Ristovski
2014-03-21 16:58     ` Jan Kratochvil
2014-03-21 17:08       ` Aleksandar Ristovski
2014-03-21 16:34   ` [PATCH v5 7/8] Validate symbol file using build-id [updated] Jan Kratochvil
2014-03-21 16:52     ` Eli Zaretskii
2014-05-20 14:51   ` [PATCH v5 7/8] Validate symbol file using build-id Tom Tromey
2014-03-19 22:31 ` [PATCH v5 3/8] Create empty common/linux-maps.[ch] and common/target-utils.[ch] Jan Kratochvil
2014-05-19 18:29   ` Tom Tromey
2014-03-19 22:31 ` [PATCH v5 2/8] Merge multiple hex conversions Jan Kratochvil
2014-05-19 18:24   ` Tom Tromey
2014-03-19 22:31 ` [PATCH v5 8/8] Tests for validate symbol file using build-id Jan Kratochvil
2014-05-20 14:57   ` Tom Tromey
2014-05-20 15:29     ` Jan Kratochvil [this message]
2014-03-19 22:31 ` [PATCH v5 6/8] gdbserver build-id attribute generator Jan Kratochvil
2014-05-20 14:40   ` Tom Tromey
2014-05-21 12:24     ` Jan Kratochvil
2014-05-21 16:48       ` Tom Tromey

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=20140520152934.GA27766@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=ARistovski@qnx.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@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