public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "alexandr.miloslavskiy at syntevo dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/29871] "p tail.y ++ (diff.y / 2)" command causes crash
Date: Mon, 20 Mar 2023 14:45:05 +0000	[thread overview]
Message-ID: <bug-29871-4717-zzmKYMpFgn@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29871-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29871

Alexandr Miloslavskiy <alexandr.miloslavskiy at syntevo dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |alexandr.miloslavskiy@synte
                   |                            |vo.com

--- Comment #5 from Alexandr Miloslavskiy <alexandr.miloslavskiy at syntevo dot com> ---
The problem was standing in my way in a completely useful usecase.

I was calling a function like this:
(gdb) call (void)0x00007ffff6e072a0()

The reason for calling it by address is that there is an ambiguous symbol name
for it:
1) libgcrypt.so - ps - some variable
2) libjvm.so    - ps - function I want to call, exported as non-debugging
symbol

And I didn't find a way to disambiguate them, see
https://sourceware.org/pipermail/gdb/2021-September/049677.html

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2023-03-20 14:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-10 21:03 [Bug gdb/29871] New: " georgebateman16 at gmail dot com
2022-12-10 22:30 ` [Bug gdb/29871] " simark at simark dot ca
2022-12-11 19:54 ` tromey at sourceware dot org
2022-12-13  5:03 ` cvs-commit at gcc dot gnu.org
2022-12-13  5:04 ` tromey at sourceware dot org
2023-03-20 14:45 ` alexandr.miloslavskiy at syntevo dot com [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=bug-29871-4717-zzmKYMpFgn@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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).