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] New: GDB 15 broke Rust upstream GDB tests
Date: Wed, 20 Mar 2024 22:33:22 +0000	[thread overview]
Message-ID: <bug-31517-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=31517

            Bug ID: 31517
           Summary: GDB 15 broke Rust upstream GDB tests
           Product: gdb
           Version: HEAD
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: rust
          Assignee: unassigned at sourceware dot org
          Reporter: liushuyu011 at gmail dot com
  Target Milestone: ---

Created attachment 15423
  --> https://sourceware.org/bugzilla/attachment.cgi?id=15423&action=edit
Error logs

Hi there,

Recently, I tried building and running Rust 1.76 testsuites on my device, and I
encountered a slew of errors when the test runner started to run GDB-related
tests.

The errors were like this: (see the log file attached).

I remember those tests passing before, so I did some digging on GDB, and I
found this commit:
https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=b0dd661fa16a424f059b1e1d80e779508b1a9a12
that caused this kind of error.

I am unsure if this new behaviour is intentional. If it is, how should someone
print out the size of a Rust slice in this case?

I have also opened a bug report on the Rust upstream:
https://github.com/rust-lang/rust/issues/122751, in case GDB cannot do anything
to fix this situation (so that Rust upstream can fix their tests instead).

Thanks!

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

             reply	other threads:[~2024-03-20 22:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-20 22:33 liushuyu011 at gmail dot com [this message]
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
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@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).