public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug testsuite/29910] New: [gdb/testsuite] FAIL: gdb.python/py-breakpoint.exp: test_hardware_breakpoints: Set hardware breakpoint
@ 2022-12-16 15:10 vries at gcc dot gnu.org
2023-01-02 9:14 ` [Bug testsuite/29910] " vries at gcc dot gnu.org
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: vries at gcc dot gnu.org @ 2022-12-16 15:10 UTC (permalink / raw)
To: gdb-prs
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.
^ permalink raw reply [flat|nested] 4+ messages in thread* [Bug testsuite/29910] [gdb/testsuite] FAIL: gdb.python/py-breakpoint.exp: test_hardware_breakpoints: Set hardware breakpoint
2022-12-16 15:10 [Bug testsuite/29910] New: [gdb/testsuite] FAIL: gdb.python/py-breakpoint.exp: test_hardware_breakpoints: Set hardware breakpoint vries at gcc dot gnu.org
@ 2023-01-02 9:14 ` 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
2 siblings, 0 replies; 4+ messages in thread
From: vries at gcc dot gnu.org @ 2023-01-02 9:14 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=29910
--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
Using -qualified fixes it:
...
diff --git a/gdb/testsuite/gdb.python/py-breakpoint.exp
b/gdb/testsuite/gdb.python/py-break
point.exp
index 397e4b31309..4065413056a 100644
--- a/gdb/testsuite/gdb.python/py-breakpoint.exp
+++ b/gdb/testsuite/gdb.python/py-breakpoint.exp
@@ -271,7 +271,7 @@ proc_with_prefix test_hardware_breakpoints { } {
delete_breakpoints
- gdb_test "python hbp1 = gdb.Breakpoint(\"add\",
type=gdb.BP_HARDWARE_BREAKPOINT)" \
+ gdb_test "python hbp1 = gdb.Breakpoint(\"add\",
type=gdb.BP_HARDWARE_BREAKPOINT
, qualified=True)" \
".*Hardware assisted breakpoint ($decimal)+ at .*$srcfile, line
($decimal)+\." \
"Set hardware breakpoint"
gdb_test "python print (gdb.breakpoints()\[0\].type ==
gdb.BP_HARDWARE_BREAKPOINT)" \
...
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 4+ messages in thread* [Bug testsuite/29910] [gdb/testsuite] FAIL: gdb.python/py-breakpoint.exp: test_hardware_breakpoints: Set hardware breakpoint
2022-12-16 15:10 [Bug testsuite/29910] New: [gdb/testsuite] FAIL: gdb.python/py-breakpoint.exp: test_hardware_breakpoints: Set hardware breakpoint vries at gcc dot gnu.org
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
2 siblings, 0 replies; 4+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2023-01-02 10:59 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=29910
--- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom de Vries <vries@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=b9877acc81ade609c503bbcff064e09d3e290a84
commit b9877acc81ade609c503bbcff064e09d3e290a84
Author: Tom de Vries <tdevries@suse.de>
Date: Mon Jan 2 11:59:17 2023 +0100
[gdb/testsuite] Fix gdb.python/py-breakpoint.exp with libstdc++ debug info
On x86_64-linux, 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
...
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=1, argv=$hex) at 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 \
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=True.
Tested on x86_64-linux.
PR testsuite/29910
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=29910
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 4+ messages in thread* [Bug testsuite/29910] [gdb/testsuite] FAIL: gdb.python/py-breakpoint.exp: test_hardware_breakpoints: Set hardware breakpoint
2022-12-16 15:10 [Bug testsuite/29910] New: [gdb/testsuite] FAIL: gdb.python/py-breakpoint.exp: test_hardware_breakpoints: Set hardware breakpoint vries at gcc dot gnu.org
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
2 siblings, 0 replies; 4+ messages in thread
From: vries at gcc dot gnu.org @ 2023-01-02 11:00 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=29910
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|NEW |RESOLVED
Target Milestone|--- |14.1
--- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> ---
Fixed by commit.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2023-01-02 11:00 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-12-16 15:10 [Bug testsuite/29910] New: [gdb/testsuite] FAIL: gdb.python/py-breakpoint.exp: test_hardware_breakpoints: Set hardware breakpoint vries at gcc dot gnu.org
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
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).