From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id ED2943858C83; Mon, 2 Jan 2023 10:59:22 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org ED2943858C83 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1672657162; bh=plHSvLHr9IohUq+mzA8lJnbBMHGGiAuAL11E4AOy8T4=; h=From:To:Subject:Date:In-Reply-To:References:From; b=moVz4Py7oAPC9YOA4bIQjV3RNplIuA9kJGg0m1aueUFVI2blx9mkCDoMVc9Ov0R2v kITPPF5w/nBXS9kwGJXwI/due8gTSJdgOSN8EfzUM6bh2LYvn2+NoQvKYX30i3R/hS vqThdqZFOX/+/JLS2ADyKD+j/K5EclWk9b9pi1is= From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug testsuite/29910] [gdb/testsuite] FAIL: gdb.python/py-breakpoint.exp: test_hardware_breakpoints: Set hardware breakpoint Date: Mon, 02 Jan 2023 10:59:22 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: testsuite X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- 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=3D29910 --- Comment #2 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Tom de Vries : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3Db9877acc81ad= e609c503bbcff064e09d3e290a84 commit b9877acc81ade609c503bbcff064e09d3e290a84 Author: Tom de Vries Date: Mon Jan 2 11:59:17 2023 +0100 [gdb/testsuite] Fix gdb.python/py-breakpoint.exp with libstdc++ debug i= nfo On x86_64-linux, I run into: ... (gdb) python hbp1 =3D gdb.Breakpoint("add", type=3Dgdb.BP_HARDWARE_BREAKPOINT)^M Hardware assisted breakpoint 2 at 0x40072e: add. (7 locations)^M (gdb) FAIL: gdb.python/py-breakpoint.exp: test_hardware_breakpoints: \ Set hardware breakpoint ... due to libstdc++ debug info: ... $ gdb -q -batch outputs/gdb.python/py-breakpoint/py-breakpoint \ -ex start \ -ex "b add" \ -ex "info break" Temporary breakpoint 1 at 0x40076a: file py-breakpoint.c, line 50. Temporary breakpoint 1, main (argc=3D1, argv=3D$hex) at py-breakpoint.c= :50 50 int foo =3D 5; Breakpoint 2 at 0x40072e: add. (7 locations) Num Type Disp Enb Address What 2 breakpoint keep y 2.1 y 0x000000000040072e in add(int) at \ py-breakpoint.c:39 2.2 y 0x00007ffff7b131de in \ (anonymous namespace)::fast_float::bigint::add at \ ../../../../../libstdc++-v3/src/c++17/fast_float/fast_float.h:1815 ... 2.7 y 0x00007ffff7b137e4 in \ (anonymous namespace)::fast_float::bigint::add at \ ../../../../../libstdc++-v3/src/c++17/fast_float/fast_float.h:1815 ... Fix this by using qualified=3DTrue. Tested on x86_64-linux. PR testsuite/29910 Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=3D29910 --=20 You are receiving this mail because: You are on the CC list for the bug.=