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: Mon, 24 Jul 2023 13:48:38 +0000	[thread overview]
Message-ID: <bug-30330-4717-umNSalrb2C@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 #7 from Tom Tromey <tromey at sourceware dot org> ---
I found this comment in
rust/compiler/rustc_codegen_llvm/src/debuginfo/metadata.rs:

/// Create debuginfo for `[T]` and `str`. These are unsized.
///
/// NOTE: We currently emit just emit the debuginfo for the element type here
/// (i.e. `T` for slices and `u8` for `str`), so that we end up with
/// `*const T` for the `data_ptr` field of the corresponding fat-pointer
/// debuginfo of `&[T]`.
///
/// It would be preferable and more accurate if we emitted a DIArray of T
/// without an upper bound instead. That is, LLVM already supports emitting
/// debuginfo of arrays of unknown size. But GDB currently seems to end up
/// in an infinite loop when confronted with such a type.


I don't recall seeing a report about this infinite loop.  I'm not exactly
sure how to reproduce it.

Anyway I tend to think the rustc debuginfo here is just bad.  I'm reluctant
to try to work around it.  It would be better if the DWARF accurately
described what is really being emitted, including some information about
where the array bounds can be found dynamically.

To implement a workaround here, I guess I'd need to know exactly which field(s)
might have to change from 'T' to 'T[]' to be correct.  I don't know how to
find this.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2023-07-24 13:48 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 [this message]
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
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-umNSalrb2C@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).