From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
	id C757B3858CD1; Tue, 19 Mar 2024 12:42:54 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C757B3858CD1
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1710852174;
	bh=y2APmF4DKxonJ/+MYKLwEv6486XATvak2UDphujwDxM=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=o0wVXhOjtUhrj5/1gGVkSVPxKYgGImBAIinIwkmZMD+SWWFAX5IxxdhVNVwF9Kkt2
	 qER74The9epf2uaI3efAYlFT5Xv3sBL1hvu6arzE+glnUL2G4k22dcqwkGILl36P//
	 D8MI7GwQwqFMZ2IOm3GomG+m6ZLUSSl4fCxL5im8=
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tdep/31486] [gdb/tdep, aarch64] Hang when hitting access
 watchpoint on M1
Date: Tue, 19 Mar 2024 12:42:54 +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: HEAD
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.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: attachments.created
Message-ID: <bug-31486-4717-qFSNPER5VD@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-31486-4717@http.sourceware.org/bugzilla/>
References: <bug-31486-4717@http.sourceware.org/bugzilla/>
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: <gdb-prs.sourceware.org>

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

--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
Created attachment 15416
  --> https://sourceware.org/bugzilla/attachment.cgi?id=3D15416&action=3Ded=
it
Tentative linux kernel PR text

(In reply to Tom de Vries from comment #0)
> Also, it seems to me that if the kernel would communicate the watchpoint
> register values (DBGBCRn_EL1 and DBGBVRn_EL1) for which it reports a trig=
ger
> to user space, it would make it trivial to determine whether and which
> watchpoint triggered (well, according to the kernel, which may still be
> wrong).  We should probably file a linux kernel PR for this.

I wrote a draft.

Any comments?

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