From: Alexander Miloslavskiy <alexandr.miloslavskiy@gmail.com>
To: Martin Simmons <qqxnjvamvxwx@dyxyl.com>
Cc: ratmice@gmail.com, gdb@sourceware.org
Subject: Re: Disambiguating symbols by module
Date: Fri, 3 Sep 2021 19:13:26 +0300 [thread overview]
Message-ID: <48ef5e7a-f255-482d-c74c-4769da5c3bf9@gmail.com> (raw)
In-Reply-To: <jev93h3ap9.fsf@dyxyl.com>
On 03.09.2021 19:06, Martin Simmons wrote:
> If the short function name is just for convenience and you can rename it
> to something longer, then you can define a short-named user command to
> call it
Thanks! Unfortunately, the code I'm debugging is outside my control.
It's the Java's JDK that comes from packet manager in Linux. The other
symbol, which stands in my way, is also outside my control.
next prev parent reply other threads:[~2021-09-03 16:13 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
2021-09-03 16:06 ` Martin Simmons
2021-09-03 16:13 ` Alexander Miloslavskiy [this message]
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=48ef5e7a-f255-482d-c74c-4769da5c3bf9@gmail.com \
--to=alexandr.miloslavskiy@gmail.com \
--cc=gdb@sourceware.org \
--cc=qqxnjvamvxwx@dyxyl.com \
--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).