From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 792633858CD1; Thu, 21 Mar 2024 14:47:07 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 792633858CD1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1711032427; bh=pkwJgEDBKuzS3UNVJP/HfKQa1rXMitmrzQBmWTFmzRI=; h=From:To:Subject:Date:In-Reply-To:References:From; b=n8kqG074fUlUGGjL3uOD9NiCGesjtdJRK5nmubaymRCCOEAslefvnqtoSPHLMmkou S78dtco7bvIb5fxW+01QRv/JL8IChXYVSud9+1UepnsTKEFDZUrp6trV0z6cKrZ4Ed 0x2uD9oDmqIhHKoSlojUwFtLJtlKXQJ6M50qViKE= From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug rust/31517] [15 Regression] GDB 15 broke Rust upstream GDB tests Date: Thu, 21 Mar 2024 14:47:06 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey at sourceware dot org X-Bugzilla-Target-Milestone: 15.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to target_milestone Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D31517 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at sourceware dot org |tromey at sourcewar= e dot org Target Milestone|--- |15.1 --- Comment #3 from Tom Tromey --- The gdb change was intentional. See bug #30330. There's also a follow-up patch that will land before gdb 15: https://sourceware.org/pipermail/gdb-patches/2024-March/207190.html This patch slightly changes the output in some cases. In fact... let's use this bug to track that patch, to make sure it really does land for 15. > If it is, how should someone print out the size of a Rust slice in this c= ase? I built vec-slices.rs and ran it under a gdb with the patch applied: (gdb) info local mut_slice =3D &mut [i64] [1, 2, 3, 4, 5] padded_struct =3D &[vec_slices::AStruct] [ vec_slices::AStruct {x: 10, y: 11, z: 12},=20 vec_slices::AStruct {x: 13, y: 14, z: 15}] padded_tuple =3D &[(i32, i16)] [(6, 7), (8, 9)] slice_of_slice =3D &[i64] [3, 4] multiple =3D &[i64] [2, 3, 4, 5] singleton =3D &[i64] [1] empty =3D &[i64] [] --=20 You are receiving this mail because: You are on the CC list for the bug.=