public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "dblaikie at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/17272] DW_TAG_GNU_template_parameter_pack
Date: Wed, 22 Mar 2023 23:54:30 +0000 [thread overview]
Message-ID: <bug-17272-4717-Q21q6L5iHU@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17272-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17272
David Blaikie <dblaikie at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dblaikie at gmail dot com
--- Comment #12 from David Blaikie <dblaikie at gmail dot com> ---
(In reply to Ed Catmur from comment #11)
> Resent just now (no changes, just a better description):
> https://sourceware.org/pipermail/gdb-patches/2023-February/196618.html
Tried testing this with Clang's debug info (based on your request
https://sourceware.org/bugzilla/show_bug.cgi?id=28946#c6 ) & at least for the
test case I had in mind/where I think the issue is visible, this patch didn't
seem to help.
Here's what I tried:
```
template<typename T, typename ...Ts>
struct single_and_pack {
};
int main() {
single_and_pack<int, int> sap;
}
```
```
clang++ pack.cpp -g
```
```
gdb ./a.out
$ start
$ ptype sap
type = struct single_and_pack<int, int> [with T = int] {
<no data fields>
}
```
There's the `T = int` part, but nothing for `Ts = {int}` or similar.
(I did get some errors about `No module named 'gdb'` in case that's relevant -
maybe something to do with how I'd build gdb)
& it's possible I've messed up some application of the patch to building gdb -
(I've had issues with lldb, for instance, where lldb is built - but it uses my
system installed lldb .so, so I was still getting the old behavior, not sure if
something similar might be happening with gdb)
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-03-22 23:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-14 20:44 [Bug symtab/17272] New: DW_TAG_GNU_template_parameter_pack dje at google dot com
2023-01-14 0:24 ` [Bug symtab/17272] DW_TAG_GNU_template_parameter_pack ed at catmur dot uk
2023-01-14 1:57 ` tromey at sourceware dot org
2023-01-14 12:58 ` ssbssa at sourceware dot org
2023-01-14 13:34 ` ed at catmur dot uk
2023-01-14 13:37 ` ed at catmur dot uk
2023-01-15 22:44 ` ed at catmur dot uk
2023-01-16 23:37 ` tromey at sourceware dot org
2023-02-04 16:29 ` ed at catmur dot uk
2023-03-22 23:54 ` dblaikie at gmail dot com [this message]
2023-07-17 21:02 ` tromey at sourceware dot org
2023-07-17 21:04 ` tromey at sourceware dot org
2023-07-17 21:13 ` tromey at sourceware dot org
2023-07-18 23:20 ` dblaikie at gmail dot com
2023-12-10 17:01 ` ssbssa at sourceware dot org
2023-12-11 7:28 ` dblaikie at gmail 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-17272-4717-Q21q6L5iHU@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).