public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/29159] gdb crashes when libstdc++ debuginfo is present but .dwz is missing
Date: Sat, 06 Apr 2024 15:37:36 +0000	[thread overview]
Message-ID: <bug-29159-4717-cVm1TaUPRI@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29159-4717@http.sourceware.org/bugzilla/>

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

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at sourceware dot org

--- Comment #1 from Tom Tromey <tromey at sourceware dot org> ---
Not sure I am reproducing this correctly, but if I rename

$ sudo mv /usr/lib/debug/.dwz/gcc-13.2.1-7.fc38.x86_64{,-xyz}


then gdb just rejects the symbol-file, which also seems unfortunate.

warning: could not find '.gnu_debugaltlink' file for
/usr/lib/debug/usr/bin/gcc-13.2.1-7.fc38.x86_64.debug
(gdb) start
could not read '.gnu_debugaltlink' section


I couldn't interrupt debuginfod quickly enough for that approach
to work.

Is this really a 'dwz' issue or just a separate debug issue?
That wasn't clear to me from the bug.

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

      reply	other threads:[~2024-04-06 15:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-20  0:38 [Bug gdb/29159] New: " amerey at redhat dot com
2024-04-06 15:37 ` tromey at sourceware dot org [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-29159-4717-cVm1TaUPRI@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).