From: Matt Rice <ratmice@gmail.com>
To: Alexander Miloslavskiy <alexandr.miloslavskiy@gmail.com>
Cc: GDB <gdb@sourceware.org>
Subject: Re: Disambiguating symbols by module
Date: Fri, 3 Sep 2021 14:31:24 +0000 [thread overview]
Message-ID: <CACTLOFqS-4zt==+UXLm7VSm8mWfrwaT+KoYgNBzG3gao+LZvCw@mail.gmail.com> (raw)
In-Reply-To: <bf00c04e-a606-a7f4-cfeb-7ee168c0c2cc@gmail.com>
On Thu, Sep 2, 2021 at 8:48 PM Alexander Miloslavskiy via Gdb
<gdb@sourceware.org> wrote:0x00007ffff6d7a3b0
>
> Hello,
>0x00007ffff6d7a3b0
> I spend much time debugging Java with GDB.
>
> In order to obtain current Java callstack, I do this:
> (gdb) call (void)ps()
>
> The problem is, the function's name is too short and gdb confuses it
> with a variable in a different library:
>
> (gdb) info var ^ps$
> File ../../cipher/blowfish.c:
> 256: static const u32 ps[18];
>
> (gdb) info function ^ps$
> Non-debugging symbols:
> 0x00007ffff6d7a3b0 ps
>
> Here, the symbol I want is a non-debugging symbol. This also means that
> I can't disambiguate it by the source file name.
>
> Is there a syntax to disambiguate the symbol?
Been a while since I've needed to do this, but IIRC you can just set a
breakpoint using the symbol address too, like:
(gdb) break *0x00007ffff6d7a3b0
I don't know of or believe there is any nicer syntax like
object_file.o:symbol_name, which one could imagine might be possible.
next prev parent reply other threads:[~2021-09-03 14:31 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 [this message]
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
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='CACTLOFqS-4zt==+UXLm7VSm8mWfrwaT+KoYgNBzG3gao+LZvCw@mail.gmail.com' \
--to=ratmice@gmail.com \
--cc=alexandr.miloslavskiy@gmail.com \
--cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).