public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "blarsen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/31256] Crash with basic 'list .'
Date: Fri, 19 Jan 2024 08:44:02 +0000 [thread overview]
Message-ID: <bug-31256-4717-dQZhol2hmB@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31256-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=31256
Guinevere Larsen <blarsen at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[14 regression] Crash with |Crash with basic 'list .'
|basic 'list .' |
Status|NEW |ASSIGNED
--- Comment #3 from Guinevere Larsen <blarsen at redhat dot com> ---
I just reproduced it with upstream GDB, and see it is still there.
Sorry, when I was developing the "list ." command, I never
--- Comment #4 from Guinevere Larsen <blarsen at redhat dot com> ---
(...) I never tested with an inferior without debuginfo.
IMO, the whole "list" command doesn't handle missing debug information all too
well. I'll try to tackle both and fix this as soon as possible.
PS: sorry for double updates, it was a misclick
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2024-01-19 8:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 4:57 [Bug gdb/31256] New: [14 regression] " sam at gentoo dot org
2024-01-18 18:26 ` [Bug gdb/31256] " ssbssa at sourceware dot org
2024-01-18 18:39 ` sam at gentoo dot org
2024-01-18 19:43 ` csfore at posteo dot net
2024-01-18 22:33 ` csfore at posteo dot net
2024-01-19 8:44 ` blarsen at redhat dot com [this message]
2024-01-23 15:19 ` [Bug gdb/31256] " blarsen at redhat dot com
2024-01-23 15:43 ` csfore at posteo dot net
2024-01-23 15:59 ` cvs-commit at gcc dot gnu.org
2024-01-23 16:10 ` blarsen at redhat dot com
2024-01-23 16:25 ` cvs-commit at gcc dot gnu.org
2024-02-11 4:42 ` brobecker at gnat dot com
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-31256-4717-dQZhol2hmB@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).