From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 5CD323858C83; Wed, 12 Apr 2023 17:12:39 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5CD323858C83 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1681319559; bh=FvCTdy5W+Kcb9QGMI8ZO70X10u4Oc+/kcCFwwvV+YOc=; h=From:To:Subject:Date:In-Reply-To:References:From; b=V2qxwZdcI9TqRQULrom+GKDfZqFalNOifYCMF8+tK8lYYgvmq/7kl0lICZhhLdvaE L7PaAytQzGf4iXSykLiFUZDUjNiPkz7O8A4JtCzhCim1PwrjwtgXDNptvsPbV8UHd1 /v0WUu/NyQ5WlsqNXdIIFGmyKwLUEXk6tyyMgJRY= From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug tdep/29423] [gdb, tdep/aarch64] FAIL: gdb.base/watchpoint-unaligned.exp: continue (timeout) Date: Wed, 12 Apr 2023 17:12:38 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tdep X-Bugzilla-Version: 12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot 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: cc 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=3D29423 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tromey at sourceware dot o= rg --- Comment #20 from Tom Tromey --- 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. --=20 You are receiving this mail because: You are on the CC list for the bug.=