public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "werwolv98 at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug python/30489] New: gdb.Type.template_argument issue when using __int128 unsigned Date: Thu, 25 May 2023 13:45:35 +0000 [thread overview] Message-ID: <bug-30489-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=30489 Bug ID: 30489 Summary: gdb.Type.template_argument issue when using __int128 unsigned Product: gdb Version: 13.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: python Assignee: unassigned at sourceware dot org Reporter: werwolv98 at gmail dot com Target Milestone: --- Using the default libstdc++ pretty printer that ships with GCC 13.1, GDB fails to parse the template types of `std::variant` (and others) as soon as one of the template types used is a `__int128 unsigned`. The pretty printer seems to use `Type.template_argument(n)` under the hood which throws a `RuntimeError: syntax error` if one of the types is a unsigned int128 type. This leads to GDB not printing the template types and acts as if the variant contains no value. ``` std::variant<__uint128_t, int> a; std::variant<__int128_t, int> b; ``` ``` (gdb) print a $1 = std::variant<> [no contained value] (gdb) print b $2 = std::variant<__int128, int> [index 0] = {0} ``` -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2023-05-25 13:45 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-25 13:45 werwolv98 at gmail dot com [this message] 2023-05-25 16:03 ` [Bug python/30489] " tromey at sourceware dot org 2023-05-26 6:18 ` werwolv98 at gmail dot com 2023-05-26 19:28 ` tromey at sourceware dot org 2023-05-26 21:23 ` 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-30489-4717@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: linkBe 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).