public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "amerey at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug corefiles/31634] gdb doesn't correctly fetch the soname of shared libraries
Date: Fri, 19 Apr 2024 19:53:19 +0000	[thread overview]
Message-ID: <bug-31634-4717-VC4LF8nUM4@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31634-4717@http.sourceware.org/bugzilla/>

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

Aaron Merey <amerey at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |amerey at redhat dot com

--- Comment #2 from Aaron Merey <amerey at redhat dot com> ---
Thanks for the detailed bug report.  I tried to reproduce this but it worked
correctly for me:

    Thread 1 "gdb" hit Breakpoint 1, gdb_bfd_read_elf_soname (filename=0xea0680
"/home/amerey/test/solib/libfoo.so")
        at solib.c:1599
    1599          gdb_bfd_ref_ptr abfd = gdb_bfd_open (filename, gnutarget);
    (gdb) finish
    [...]
    Value returned is $1 = std::unique_ptr<char> = {
      get() = 0xeaa860 "libfoo.so"
    }

If you're able to upload your corefile where this fails I'll take a look at it.

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

  parent reply	other threads:[~2024-04-19 19:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-12 11:38 [Bug corefiles/31634] New: " pablogsal at gmail dot com
2024-04-12 11:39 ` [Bug corefiles/31634] " pablogsal at gmail dot com
2024-04-19 19:53 ` amerey at redhat dot com [this message]
2024-04-22 11:20 ` pablogsal at gmail dot com
2024-04-25 23:25 ` amerey at redhat dot com
2024-04-26  0:27 ` pablogsal at gmail dot com
2024-04-26 14:39 ` sam at gentoo dot org

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-31634-4717-VC4LF8nUM4@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).