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 rust/30330] GDB 13.1 no longer prints length of Rust slice wrappers Date: Fri, 28 Jul 2023 21:31:45 +0000 [thread overview] Message-ID: <bug-30330-4717-WSbz2toPBH@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30330-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30330 --- Comment #8 from Tom Tromey <tromey at sourceware dot org> --- Unsized types doc'd here: https://doc.rust-lang.org/book/ch19-04-advanced-types.html#dynamically-sized-types-and-the-sized-trait I don't know why I keep not understanding this but I think I finally figured it out. (gdb) ptype a type = struct &prog::Foo<[u8]> { struct prog::Foo<[u8]> *data_ptr; usize length; } So here, gdb should change the type of 'data_ptr' to 'struct prog::Foo<[u8; ...length...]> *' This can't readily be expressed in DWARF I think. But gdb can apply the change by itself. So then all that remains is fixing up the instance not to use 'u8' (but rather 'u8[]') as the type of the "VLA" part. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-07-28 21:31 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-10 20:45 [Bug rust/30330] New: " jistone at redhat dot com 2023-04-10 21:33 ` [Bug rust/30330] " tromey at sourceware dot org 2023-04-11 11:47 ` tromey at sourceware dot org 2023-04-11 18:52 ` jistone at redhat dot com 2023-04-14 3:19 ` tromey at sourceware dot org 2023-04-14 4:25 ` tromey at sourceware dot org 2023-04-14 15:47 ` jistone at redhat dot com 2023-04-14 22:03 ` tromey at sourceware dot org 2023-07-24 13:48 ` tromey at sourceware dot org 2023-07-28 21:31 ` tromey at sourceware dot org [this message] 2023-12-08 16:34 ` michaelwoerister at posteo dot net 2023-12-08 21:34 ` tromey at sourceware dot org 2023-12-08 21:36 ` tromey at sourceware dot org 2023-12-08 21:43 ` tromey at sourceware dot org 2023-12-08 21:49 ` tromey at sourceware dot org 2023-12-11 10:27 ` michaelwoerister at posteo dot net 2023-12-11 10:32 ` michaelwoerister at posteo dot net 2024-01-30 18:24 ` tromey at sourceware dot org 2024-01-30 20:33 ` jistone at redhat dot com 2024-01-31 20:57 ` tromey at sourceware dot org 2024-02-01 19:42 ` tromey at sourceware dot org 2024-02-02 18:20 ` tromey at sourceware dot org 2024-02-02 18:21 ` tromey at sourceware dot org 2024-02-20 20:57 ` cvs-commit at gcc dot gnu.org 2024-02-20 20:58 ` tromey at sourceware dot org 2024-04-02 17:44 ` cvs-commit at gcc dot gnu.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-30330-4717-WSbz2toPBH@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).