From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 0CA153858C55; Thu, 21 Mar 2024 23:26:18 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0CA153858C55 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1711063579; bh=Hz4mScANluOH0qwH4PkA6uIH4W+F3PCEBPP6fZcQJoE=; h=From:To:Subject:Date:In-Reply-To:References:From; b=fnQEGY8qCFOzCj63wfDF3KpXoTe103/UNVWk+dGvQMz89YhZX3gKGknXgCOv0I9Vh Vc5JymVbkh0U7B3JveL656F+x+4GS8uP4jJ+8S8neQzSTjlPOKKRdiFH7hdkNvH+m5 sF50+zZld5ZZ7Q1MYGs92JWjpLvNiUJDE/jyzKKk= 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 23:26:18 +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: 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 --- Comment #5 from Tom Tromey --- (In reply to liushuyu from comment #4) > Although I am curious about how to print the length of a slice like using > `print slice.length` before? You can't, not directly anyway. In Rust you use len() but the Rust compiler doesn't emit enough information for gdb to do calls via traits. > I have also built a GDB with the patch applied; the auto-completion in the > interactive mode still completes `.length` in this case: >=20 > (gdb) p multiple. > data_ptr length=20=20=20=20 >=20 > Is this expected? No, this should have a separate report. The completer still sees the underlying C-like type. --=20 You are receiving this mail because: You are on the CC list for the bug.=