public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "simon.marchi at polymtl dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/31478] GDB crashes when corrupted debuginfo
Date: Thu, 14 Mar 2024 01:25:55 +0000	[thread overview]
Message-ID: <bug-31478-4717-z60G9CJ0vE@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31478-4717@http.sourceware.org/bugzilla/>

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

Simon Marchi <simon.marchi at polymtl dot ca> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
                 CC|                            |simon.marchi at polymtl dot ca
     Ever confirmed|0                           |1
   Last reconfirmed|                            |2024-03-14

--- Comment #9 from Simon Marchi <simon.marchi at polymtl dot ca> ---
I'm on Arch too, I was able to reproduce the crash with the following steps:

 - install the kstatusnotifieritem package version 6.0.0-2
 - copy the attached debuginfo file at
~/.cache/debuginfod_client/c0b747f77ce7222a94ecae5e362d140fb5432461/debuginfo
 - run `gdb /usr/lib/libKF6StatusNotifierItem.so.6.0.0` and answer yes when
asked if I want to use debuginfod

I guess that it should be possible to reproduce on other distros too by
downloading the package [1] and extracting the so file.

[1]
https://archive.archlinux.org/packages/k/kstatusnotifieritem/kstatusnotifieritem-6.0.0-2-x86_64.pkg.tar.zst

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

  parent reply	other threads:[~2024-03-14  1:25 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
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 [this message]
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-z60G9CJ0vE@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).