public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "liushuyu011 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug rust/31517] [15 Regression] GDB 15 broke Rust upstream GDB tests
Date: Thu, 21 Mar 2024 21:42:26 +0000 [thread overview]
Message-ID: <bug-31517-4717-4SndzckP7a@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31517-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=31517
--- Comment #4 from liushuyu <liushuyu011 at gmail dot com> ---
> I built vec-slices.rs and ran it under a gdb with the patch
> applied:
Thanks for the information!
Although I am curious about how to print the length of a slice like using
`print slice.length` before?
I have also built a GDB with the patch applied; the auto-completion in the
interactive mode still completes `.length` in this case:
(gdb) p multiple.
data_ptr length
Is this expected?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2024-03-21 21:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-20 22:33 [Bug rust/31517] New: " liushuyu011 at gmail dot com
2024-03-20 22:37 ` [Bug rust/31517] " liushuyu011 at gmail dot com
2024-03-20 22:40 ` doko at debian dot org
2024-03-20 22:41 ` [Bug rust/31517] [15 Regression] " doko at debian dot org
2024-03-20 22:42 ` doko at debian dot org
2024-03-21 14:47 ` tromey at sourceware dot org
2024-03-21 21:42 ` liushuyu011 at gmail dot com [this message]
2024-03-21 23:26 ` tromey at sourceware dot org
2024-03-23 3:56 ` [Bug rust/31517] [15 Regression] Rust upstream GDB tests regressions with GDB 15 brobecker at gnat dot com
2024-03-23 3:59 ` brobecker at gnat dot com
2024-03-23 15:20 ` tromey at sourceware dot org
2024-04-02 17:44 ` cvs-commit at gcc dot gnu.org
2024-04-02 17:45 ` tromey at sourceware dot 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-31517-4717-4SndzckP7a@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).