This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH v5 8/8] Tests for validate symbol file using build-id
- From: Tom Tromey <tromey at redhat dot com>
- To: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- Cc: gdb-patches at sourceware dot org, Aleksandar Ristovski <ARistovski at qnx dot com>
- Date: Tue, 20 May 2014 08:57:11 -0600
- Subject: Re: [PATCH v5 8/8] Tests for validate symbol file using build-id
- Authentication-results: sourceware.org; auth=none
- References: <20140319223004 dot 14668 dot 20989 dot stgit at host1 dot jankratochvil dot net> <20140319223131 dot 14668 dot 9029 dot stgit at host1 dot jankratochvil dot net>
>>>>> "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?
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?
How does the new functionality interact with the existing build-id
functionality?
Tom