[Bug tdep/29423] [gdb, tdep/aarch64] FAIL: gdb.base/watchpoint-unaligned.exp: continue (timeout)

["tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=29423

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at sourceware dot org

--- Comment #20 from Tom Tromey <tromey at sourceware dot org> ---
I found another way to see watchpoint problems on aarch64.
Edit testsuite/gdb.ada/task_watch.exp and change the final
breakpoint to a plain continue:

diff --git a/gdb/testsuite/gdb.ada/task_watch.exp
b/gdb/testsuite/gdb.ada/task_watch.exp
index 0641008fb51..fedcf5073dc 100644
--- a/gdb/testsuite/gdb.ada/task_watch.exp
+++ b/gdb/testsuite/gdb.ada/task_watch.exp
@@ -80,6 +80,7 @@ gdb_test "info tasks" \
 # Now, resume the execution and make sure that GDB does not stop when
 # task 4 hits the watchpoint. Continuing thus results in our program
 # running to completion.
-set bp_location [gdb_get_line_number "STOP_HERE_2" ${testdir}/foo.adb]
-gdb_breakpoint foo.adb:$bp_location
-gdb_continue_to_breakpoint second ".*foo.adb:$bp_location.*null; --
STOP_HERE_2"
+# set bp_location [gdb_get_line_number "STOP_HERE_2" ${testdir}/foo.adb]
+# gdb_breakpoint foo.adb:$bp_location
+# gdb_continue_to_breakpoint second ".*foo.adb:$bp_location.*null; --
STOP_HERE_2"
+gdb_test "continue"


Now run the test.


I get:

continue
Continuing.
[Thread 0xfffff7e031d0 (LWP 104664) exited]
[Thread 0xfffff79f11d0 (LWP 104666) exited]
[Thread 0xfffff7bfa1d0 (LWP 104665) exited]
FAIL: gdb.ada/task_watch.exp: continue (timeout)


I think this is hitting the watchpoint but then getting confused.
I haven't really debugged any further.

-- 
You are receiving this mail because:
You are on the CC list for the bug.