From: Aleksandar Ristovski <ARistovski@qnx.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>,
Pedro Alves <palves@redhat.com>
Cc: Eli Zaretskii <eliz@gnu.org>, "dje@google.com" <dje@google.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH v9 09/10] Validate symbol file using build-id
Date: Mon, 13 Jul 2015 12:48:00 -0000 [thread overview]
Message-ID: <20150713124827.6594646.10106.9093@qnx.com> (raw)
Original Message
From: Jan Kratochvil
Sent: Monday, July 13, 2015 08:38
To: Pedro Alves
Cc: Eli Zaretskii; dje@google.com; gdb-patches@sourceware.org; Aleksandar Ristovski
Subject: Re: [PATCH v9 09/10] Validate symbol file using build-id
...
[Jan] OK, so validate-build-id or solib-validate-build-id.
...
[AR]
I vote for validate-build-id
It will apply to exe as well. Description may contain a note that currently validation does not work on exes.
next reply other threads:[~2015-07-13 12:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 12:48 Aleksandar Ristovski [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-06-14 19:25 [PATCH v7 00/10] Validate binary before use Jan Kratochvil
2015-06-14 19:27 ` [PATCH v7 09/10] Validate symbol file using build-id Jan Kratochvil
2015-06-21 10:16 ` [PATCH v8 " Jan Kratochvil
2015-06-22 22:25 ` Doug Evans
2015-06-23 20:47 ` Jan Kratochvil
2015-07-08 14:44 ` Pedro Alves
2015-07-12 19:09 ` Jan Kratochvil
2015-07-12 19:29 ` [PATCH v9 " Jan Kratochvil
2015-07-12 19:54 ` Eli Zaretskii
2015-07-12 20:01 ` Jan Kratochvil
2015-07-13 2:30 ` Eli Zaretskii
2015-07-13 10:34 ` Pedro Alves
2015-07-13 12:38 ` Jan Kratochvil
2015-07-14 16:14 ` Doug Evans
2015-07-15 8:21 ` Jan Kratochvil
2015-07-15 14:59 ` Doug Evans
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=20150713124827.6594646.10106.9093@qnx.com \
--to=aristovski@qnx.com \
--cc=dje@google.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=palves@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).