public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "jengelh at inai dot de" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/28946] New: Missing template paramater pack support Date: Sat, 05 Mar 2022 16:08:13 +0000 [thread overview] Message-ID: <bug-28946-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=28946 Bug ID: 28946 Summary: Missing template paramater pack support Product: gdb Version: 11.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: jengelh at inai dot de Target Milestone: --- Input ===== ``` template<typename... T> void f(T&&...zzargs) {} int main() { f(0); } ``` g++-11 -Wall -ggdb3 x.cpp Observed output =============== » gdb a.out GNU gdb (GDB; openSUSE Tumbleweed) 11.1 ... (gdb) b main (gdb) r ... Breakpoint 1, main () at x.cpp:2 2 int main() { f(0); } Missing separate debuginfos, use: zypper install libgcc_s1-debuginfo-11.2.1+git1173-2.3.x86_64 libstdc++6-debuginfo-11.2.1+git1173-2.3.x86_64 (gdb) s f<int> () at x.cpp:1 1 template<typename... T> void f(T&&...zzargs) {} (gdb) info args No arguments. (gdb) p zzargs No symbol "zzargs" in current context. Expected output =============== (gdb) info args zzargs = {0} (gdb) p zzargs $1 = {0} or something of the sort. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-03-05 16:08 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-05 16:08 jengelh at inai dot de [this message] 2022-03-06 14:20 ` [Bug gdb/28946] " ssbssa at sourceware dot org 2022-03-06 14:55 ` ssbssa at sourceware dot org 2022-03-06 16:49 ` [Bug c++/28946] " tromey at sourceware dot org 2022-10-27 21:56 ` dblaikie at gmail dot com 2023-01-14 12:58 ` ssbssa at sourceware dot org 2023-01-14 19:13 ` dblaikie at gmail dot com 2023-01-16 23:37 ` tromey at sourceware dot org 2023-01-17 1:00 ` ed at catmur dot uk
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-28946-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).