From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 228A5385770B; Wed, 12 Apr 2023 13:12:58 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 228A5385770B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1681305178; bh=gU/jrJVlWyscMyefjRgAuPsrBslqKS9/h+ncHkBTHHY=; h=From:To:Subject:Date:In-Reply-To:References:From; b=KWMoJx5YIdJdduONRkGrzvJBhz0GovQunFCLQQa7spvta/DwtfUabrDA4cTkxXRR+ ntY7MfDN1n3n9OXHybFijiWpsiN7CRDcS+QQSxAN8a6mbul/HFSnRxhPfyxTDSxrjd Cr7oTXIo9LiZ9aDe85FgpScjeeAxo01I1SMmcQH4= From: "luis.machado at arm dot com" 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 13:12:57 +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: luis.machado at arm dot com 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: bug_status 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 Luis Machado changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |NEW --- Comment #18 from Luis Machado --- Thanks! That gives me a good indication of what's going wrong. Looks like these blocks in gdb/nat/aarch64-linux-hw-point.c:aarch64_linux_get_debug_reg_capacity are failing: if (ptrace (PTRACE_GETREGSET, tid, NT_ARM_HW_WATCH, &iov) =3D=3D 0 && compatible_debug_arch (AARCH64_DEBUG_ARCH (dreg_state.dbg_info))) and if (ptrace (PTRACE_GETREGSET, tid, NT_ARM_HW_BREAK, &iov) =3D=3D 0 && compatible_debug_arch (AARCH64_DEBUG_ARCH (dreg_state.dbg_info))) I suppose ptrace wouldn't fail, so I'm guessing compatible_debug_arch might= be the culprit, since it checks a hardcoded number of variations of AARCH64_DEBUG_ARCH_V8*, and we may be returning false if the AARCH64_DEBUG_= ARCH is outside of the expected range. We might need a new bug for this. --=20 You are receiving this mail because: You are on the CC list for the bug.=