From: Pedro Alves <palves@redhat.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/3] Make exec-file-mismatch compare build IDs
Date: Sun, 17 May 2020 19:04:47 +0100 [thread overview]
Message-ID: <20200517180450.14925-1-palves@redhat.com> (raw)
The patch series makes GDB first try exec-file-mismatch validation via
build IDs, and then if that isn't possible, fallback to validating
using the old method of comparing filenames. I'd argue that we should
remove the filename validation for causing too many false positives,
though.
See full details on patch #3. Patches #1 and #2 and simple
preparatory patches.
Patch #3 contains manual and NEWS changes.
Pedro Alves (3):
Default gdb_bfd_open's fd parameter to -1
Eliminate target_fileio_open_warn_if_slow
Make exec-file-mismatch compare build IDs
gdb/doc/gdb.texinfo | 23 ++++++++++++----------
gdb/NEWS | 15 +++++++-------
gdb/build-id.c | 2 +-
gdb/compile/compile-object-load.c | 2 +-
gdb/dwarf2/read.c | 4 ++--
gdb/exec.c | 41 +++++++++++++++++++++++++++++++++++++--
gdb/gdb_bfd.c | 28 ++++++++++++++++----------
gdb/gdb_bfd.h | 7 +++++--
gdb/machoread.c | 4 ++--
gdb/solib-darwin.c | 2 +-
gdb/symfile.c | 6 +++---
gdb/target.c | 33 +++++--------------------------
gdb/target.h | 20 +++++++------------
gdb/windows-nat.c | 2 +-
gdb/windows-tdep.c | 2 +-
15 files changed, 106 insertions(+), 85 deletions(-)
base-commit: 7cfd74cfc6e14034779e6cc048c68877b7a08f88
--
2.14.5
next reply other threads:[~2020-05-17 18:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-17 18:04 Pedro Alves [this message]
2020-05-17 18:04 ` [PATCH 1/3] Default gdb_bfd_open's fd parameter to -1 Pedro Alves
2020-05-17 18:04 ` [PATCH 2/3] Eliminate target_fileio_open_warn_if_slow Pedro Alves
2020-05-17 18:04 ` [PATCH 3/3] Make exec-file-mismatch compare build IDs Pedro Alves
2020-05-17 18:25 ` Eli Zaretskii
2020-05-18 13:52 ` Pedro Alves
2020-05-18 13:55 ` [PATCH v2 " Pedro Alves
2020-05-18 14:21 ` Philippe Waroquiers
2020-05-19 15:43 ` Pedro Alves
2020-05-19 16:04 ` Tom Tromey
2020-05-19 17:44 ` Pedro Alves
2020-05-21 13:32 ` Philippe Waroquiers
2020-05-21 14:02 ` Pedro Alves
2020-05-21 14:23 ` Philippe Waroquiers
2020-05-21 14:27 ` Pedro Alves
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=20200517180450.14925-1-palves@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
/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