public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Alexander Miloslavskiy <alexandr.miloslavskiy@gmail.com>
To: Christian Biesinger <cbiesinger@google.com>
Cc: Reuben Thomas via Gdb <gdb@sourceware.org>
Subject: Re: Disambiguating symbols by module
Date: Fri, 3 Sep 2021 23:58:58 +0300	[thread overview]
Message-ID: <240ffeee-871c-92ff-dff1-6fcfc04ef159@gmail.com> (raw)
In-Reply-To: <CAPTJ0XFOUJcg6ZEohzYwoqudkvC=+LKSpxsKtLdjFw7edGuxbA@mail.gmail.com>

On 03.09.2021 19:25, Christian Biesinger wrote:
> The python API lets you do this:
> gdb.lookup_objfile("libfoo").lookup_global_symbol("ps")

Thanks! Unfortunately it seems that gdb does not return non-debugging 
symbols this way. I can get the offending symbol with this approach, but 
not the desired one.

Anyways, while trying that, I figured that the offending symbol comes 
from a dbgsym package that I never meant to install. It somehow slipped 
through to my machine two years ago, too late to figure how it happened. 
After uninstalling it, there is no longer the other symbol to confuse 
gdb, so I can now simply

(gdb) call (void)ps()

This means that my problem is now solved.

      reply	other threads:[~2021-09-03 20:59 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
2021-09-03 16:25 ` Christian Biesinger
2021-09-03 20:58   ` Alexander Miloslavskiy [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=240ffeee-871c-92ff-dff1-6fcfc04ef159@gmail.com \
    --to=alexandr.miloslavskiy@gmail.com \
    --cc=cbiesinger@google.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).