public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.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: Tue, 20 Feb 2024 20:57:30 +0000 [thread overview] Message-ID: <bug-30330-4717-5CE3sxeRVZ@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 #22 from Sourceware Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Tom Tromey <tromey@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=b0dd661fa16a424f059b1e1d80e779508b1a9a12 commit b0dd661fa16a424f059b1e1d80e779508b1a9a12 Author: Tom Tromey <tromey@adacore.com> Date: Tue Jan 30 10:06:46 2024 -0700 Rewrite Rust slice type handling This patch rewrites the handling of slice types in Rust. More recent versions of the Rust compiler changed how unsized types were emitted, letting gdb inspect them more nicely. However, gdb did not do this, and in fact treated all such types as if they were slices of arrays, which is incorrect. This patch rewrites this handling and removes the restriction that unsized types must be array slices. I've added a comment explaining how unsized types are represented to rust-lang.c as well. I looked into a different approach, namely changing the DWARF reader to fix up slice types to have a dynamic type. However, the approach taken here turned out to be simpler. Tested on x86-64 Fedora 38 with a variety of Rust compiler versions. Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30330 -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-02-20 20:57 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 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 [this message] 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-5CE3sxeRVZ@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).