From: Alexander Miloslavskiy <alexandr.miloslavskiy@gmail.com>
To: Matt Rice <ratmice@gmail.com>
Cc: GDB <gdb@sourceware.org>
Subject: Re: Disambiguating symbols by module
Date: Fri, 3 Sep 2021 17:57:42 +0300 [thread overview]
Message-ID: <4e230740-b655-bdc3-dbe0-b1ed518d1a26@gmail.com> (raw)
In-Reply-To: <CACTLOFrNX5BY7S9cLV5H1sZpWnNs6H_U7eZ2HH6AP8cNMfXXTQ@mail.gmail.com>
On 03.09.2021 17:53, Matt Rice wrote:
> I don't really know of any satisfactory solution then...
> The best workaround I can come up with is to put the address in a
> convience variable (which could perhaps be automated with some python
> scripts in your gdbinit, to gain some address independence).
Right, I think that a startup python script could work, if there are no
better solutions. Thanks!
next prev parent reply other threads:[~2021-09-03 14:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-02 20:48 Alexander Miloslavskiy
2021-09-03 14:31 ` Matt Rice
2021-09-03 14:35 ` Alexander Miloslavskiy
2021-09-03 14:53 ` Matt Rice
2021-09-03 14:57 ` Alexander Miloslavskiy [this message]
2021-09-03 16:06 ` Martin Simmons
2021-09-03 16:13 ` Alexander Miloslavskiy
2021-09-03 16:25 ` Christian Biesinger
2021-09-03 20:58 ` Alexander Miloslavskiy
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=4e230740-b655-bdc3-dbe0-b1ed518d1a26@gmail.com \
--to=alexandr.miloslavskiy@gmail.com \
--cc=gdb@sourceware.org \
--cc=ratmice@gmail.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).