public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "davispuh at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/31478] GDB crashes when corrupted debuginfo
Date: Wed, 13 Mar 2024 10:12:11 +0000	[thread overview]
Message-ID: <bug-31478-4717-ge7TSRjry6@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31478-4717@http.sourceware.org/bugzilla/>

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

--- Comment #3 from Dāvis Mosāns <davispuh at gmail dot com> ---
Created attachment 15402
  --> https://sourceware.org/bugzilla/attachment.cgi?id=15402&action=edit
Crashing debuginfo

(In reply to Aaron Merey from comment #2)
> This may be difficult to reproduce.  Do you have an environment set up where
> 'gdb program' with debuginfod enabled reliably crashes when
> ~/.cache/debuginfod_client is removed?

No it doesn't crash if I remove `~/.cache/debuginfod_client` because issue is
purely with some corrupted file there.

I now narrowed it down to
~/.cache/debuginfod_client/c0b747f77ce7222a94ecae5e362d140fb5432461/debuginfo
(attached here)

I'm not sure if you can reproduce crash since it probably depends on exact
program/libraries but you can try using Arch Linux, copying given debuginfo
file and then running
> DEBUGINFOD_URLS=https://debuginfod.archlinux.org gdb konsole -ex "set debuginfod enabled on" -ex "run"

konsole is from KDE (pacman -S konsole)

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

  parent reply	other threads:[~2024-03-13 10:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-12 19:38 [Bug gdb/31478] New: " davispuh at gmail dot com
2024-03-12 20:00 ` [Bug gdb/31478] " davispuh at gmail dot com
2024-03-12 22:40 ` amerey at redhat dot com
2024-03-13 10:12 ` davispuh at gmail dot com [this message]
2024-03-13 15:49 ` tromey at sourceware dot org
2024-03-13 18:53 ` davispuh at gmail dot com
2024-03-13 19:30 ` tromey at sourceware dot org
2024-03-13 20:16 ` amerey at redhat dot com
2024-03-13 20:20 ` amerey at redhat dot com
2024-03-13 21:49 ` davispuh at gmail dot com
2024-03-14  1:25 ` simon.marchi at polymtl dot ca
2024-03-14 13:10 ` tromey at sourceware 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-31478-4717-ge7TSRjry6@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).