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/30651] GDB crash on _BitInt debuginfo
Date: Thu, 20 Jul 2023 22:12:54 +0000 [thread overview]
Message-ID: <bug-30651-4717-uSBYoORxpq@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30651-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30651
--- Comment #6 from Tom Tromey <tromey at sourceware dot org> ---
(In reply to Jakub Jelinek from comment #4)
> Yeah. I've filed https://dwarfstd.org/issues/230529.1.html proposal for
> DWARF6, but it hasn't been discussed yet. And, while GDB can print some
> _BitInt values just fine (seems if they are multiple of 64 bits, it gives up
> on others. Right now when debugging stuff I'm just printing the limbs using
> x/<N>gx &var when GDB can't handle it.
It looks like there are new suffixes too? And the semantics of these aren't
identical to existing int types? And I guess new ABI... probably will end
up wanting several gdb bugs to implement it all.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-07-20 22:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 17:33 [Bug gdb/30651] New: " jakub at redhat dot com
2023-07-18 17:33 ` [Bug gdb/30651] " jakub at redhat dot com
2023-07-18 21:35 ` tromey at sourceware dot org
2023-07-20 21:31 ` tromey at sourceware dot org
2023-07-20 21:57 ` jakub at redhat dot com
2023-07-20 22:11 ` tromey at sourceware dot org
2023-07-20 22:12 ` tromey at sourceware dot org [this message]
2023-07-21 20:20 ` cvs-commit at gcc dot gnu.org
2023-07-21 20:21 ` 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-30651-4717-uSBYoORxpq@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).