From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
To: Pedro Alves <palves@redhat.com>,
"Metzger, Markus T" <markus.t.metzger@intel.com>,
GDB <gdb@sourceware.org>
Subject: Re: exec-file-mismatch and native-gdbserver testing
Date: Sun, 17 May 2020 07:24:13 +0200 [thread overview]
Message-ID: <ee8a2cc2b45fca508da399fd41583640a72a065a.camel@skynet.be> (raw)
In-Reply-To: <c64413bf-532c-7ad5-0f57-53c40074976d@redhat.com>
On Sat, 2020-05-16 at 21:10 +0100, Pedro Alves via Gdb wrote:
>
> So I cooked up something. Below's the resulting preliminary patch.
>
> Seems to work nicely -- it fixes gdb.base/argv0-symlink.exp at least.
> I haven't run the testsuite yet.
I have looked at the patch and played a little bit in a native setup.
It worked as expected, the patch looks ok to me.
Note that buildid comparison means that the exec-file used by
GDB might not be the (same physical) exec-file of the process
being debugged.
For some specific scenarios, it might have an impact,
such as the user wanting to debug a copy of the file to avoid
'Text file busy', maybe some interaction with setuid/setgid, ... ?
Maybe good enough to mention this in the user manual and/or in the
'help set exec-file-
mismatch' ?
Or maybe GDB should give a message to the user for different files
but same buildid ?
>
> There's (at least) one issue that I'll need to fix. It's to
> get rid of the "transfers from remote targets can be slow" warning
> when we open the remote file to read the build id:
Note that before GDB 10 goes out with this new exec-file-mismatch feature,
we should sort out: https://sourceware.org/bugzilla/show_bug.cgi?id=25475
as possibly fixing this bug might imply to change the options of
'set exec-file-mismatch'
(see last comment in the bug).
Thanks
Philippe
next prev parent reply other threads:[~2020-05-17 5:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-08 14:02 Metzger, Markus T
2020-04-08 20:54 ` Philippe Waroquiers
2020-04-09 6:30 ` Metzger, Markus T
2020-05-08 10:30 ` Metzger, Markus T
2020-05-08 21:25 ` Philippe Waroquiers
2020-05-16 20:10 ` Pedro Alves
2020-05-17 5:24 ` Philippe Waroquiers [this message]
2020-05-17 17:47 ` Pedro Alves
2020-05-17 18:15 ` Philippe Waroquiers
2020-05-17 19:50 ` Pedro Alves
2020-05-17 20:11 ` Philippe Waroquiers
2020-05-17 21:19 ` Pedro Alves
2020-05-17 21:43 ` Philippe Waroquiers
2020-05-17 21:58 ` Pedro Alves
2020-05-18 10:35 ` Philippe Waroquiers
2020-05-18 14:05 ` 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=ee8a2cc2b45fca508da399fd41583640a72a065a.camel@skynet.be \
--to=philippe.waroquiers@skynet.be \
--cc=gdb@sourceware.org \
--cc=markus.t.metzger@intel.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).