From: Tom Tromey <tom@tromey.com>
To: "Christian Biesinger via gdb-patches" <gdb-patches@sourceware.org>
Cc: Philippe Waroquiers <philippe.waroquiers@skynet.be>,
Christian Biesinger <cbiesinger@google.com>
Subject: Re: [RFA 3/3] Document 'set|show exec-file-mismatch (reload|warn|off)'
Date: Wed, 08 Jan 2020 00:52:00 -0000 [thread overview]
Message-ID: <87a76yrcqr.fsf@tromey.com> (raw)
In-Reply-To: <CAPTJ0XFS8ey34xpdHxU-uX_qiyLxv3WoQPpa1_hXu_eB5LNkUQ@mail.gmail.com> (Christian Biesinger via gdb-patches's message of "Sat, 21 Dec 2019 21:46:28 -0500")
Christian> When would someone set this to off, or even warn? I'm wondering is it makes
Christian> sense to add this setting vs always having the reload behavior?
Last time this stuff came up, it turned out there are users who point
gdb at the file with debug symbols while debugging a stripped version on
the target. IIRC, at the time, build-id and separate debuginfo weren't
widely used, so this was the main way to do this kind of thing.
I don't know if this is still important. I've only run into trouble
with this behavior, so I welcome the new default at least.
Tom
prev parent reply other threads:[~2020-01-08 0:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-21 14:36 [RFA 1/3] New option 'set exec-file-mismatch (reload|warn|off)'. Fixes PR gdb/17626 Philippe Waroquiers
2019-12-21 14:36 ` [RFA 2/3] Test 'set exec-file-mismatch reload|warn|off' Philippe Waroquiers
2019-12-21 14:36 ` [RFA 1/3] Implement 'set/show exec-file-mismatch' Philippe Waroquiers
2020-01-08 0:58 ` Tom Tromey
2019-12-21 14:36 ` [RFA 3/3] Document 'set|show exec-file-mismatch (reload|warn|off)' Philippe Waroquiers
2019-12-21 17:44 ` Eli Zaretskii
2019-12-21 20:16 ` Philippe Waroquiers
2019-12-22 18:20 ` Eli Zaretskii
2019-12-22 2:46 ` Christian Biesinger via gdb-patches
2019-12-22 9:09 ` Philippe Waroquiers
2020-01-08 0:52 ` Tom Tromey [this message]
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=87a76yrcqr.fsf@tromey.com \
--to=tom@tromey.com \
--cc=cbiesinger@google.com \
--cc=gdb-patches@sourceware.org \
--cc=philippe.waroquiers@skynet.be \
/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