public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/29910] New: [gdb/testsuite] FAIL: gdb.python/py-breakpoint.exp: test_hardware_breakpoints: Set hardware breakpoint
Date: Fri, 16 Dec 2022 15:10:58 +0000 [thread overview]
Message-ID: <bug-29910-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29910
Bug ID: 29910
Summary: [gdb/testsuite] FAIL: gdb.python/py-breakpoint.exp:
test_hardware_breakpoints: Set hardware breakpoint
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: testsuite
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
I run into:
...
(gdb) python hbp1 = gdb.Breakpoint("add", type=gdb.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
...
Presumably 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
/home/vries/gdb_versions/devel/src/gdb/testsuite/gdb.python/py-breakpoint.c,
line 50.
Temporary breakpoint 1, main (argc=1, argv=0x7fffffffdbe8) at
/home/vries/gdb_versions/devel/src/gdb/testsuite/gdb.python/py-breakpoint.c:50
50 int foo = 5;
Breakpoint 2 at 0x40072e: add. (7 locations)
Num Type Disp Enb Address What
2 breakpoint keep y <MULTIPLE>
2.1 y 0x000000000040072e in add(int) at
/home/vries/gdb_versions/devel/src/gdb/testsuite/gdb.python/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.3 y 0x00007ffff7b132a8 in (anonymous
namespace)::fast_float::bigint::add at
../../../../../libstdc++-v3/src/c++17/fast_float/fast_float.h:1815
2.4 y 0x00007ffff7b133e0 in (anonymous
namespace)::fast_float::bigint::add at
../../../../../libstdc++-v3/src/c++17/fast_float/fast_float.h:1771
2.5 y 0x00007ffff7b133fd in (anonymous
namespace)::fast_float::bigint::add at
../../../../../libstdc++-v3/src/c++17/fast_float/fast_float.h:1648
2.6 y 0x00007ffff7b1363d 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
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-12-16 15:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 15:10 vries at gcc dot gnu.org [this message]
2023-01-02 9:14 ` [Bug testsuite/29910] " vries at gcc dot gnu.org
2023-01-02 10:59 ` cvs-commit at gcc dot gnu.org
2023-01-02 11:00 ` vries at gcc dot gnu.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-29910-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).