public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
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 [thread overview]
Message-ID: <bug-31486-4717-qFSNPER5VD@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31486-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=31486
--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
Created attachment 15416
--> https://sourceware.org/bugzilla/attachment.cgi?id=15416&action=edit
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 trigger
> 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?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2024-03-19 12:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-14 12:39 [Bug tdep/31486] New: " vries at gcc dot gnu.org
2024-03-14 12:39 ` [Bug tdep/31486] " vries at gcc dot gnu.org
2024-03-19 9:04 ` vries at gcc dot gnu.org
2024-03-19 12:42 ` vries at gcc dot gnu.org [this message]
2024-03-20 9:50 ` luis.machado at arm dot com
2024-03-22 16:26 ` vries at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-31486-4717-qFSNPER5VD@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).