public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "ahajkova at redhat dot com" <sourceware-bugzilla@sourceware.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 20:59:10 +0000 [thread overview]
Message-ID: <bug-29423-4717-rGgKtMT7wp@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29423-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29423
--- Comment #22 from Alexandra Hájková <ahajkova at redhat dot com> ---
(In reply to Luis Machado from comment #18)
> 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) == 0
> && compatible_debug_arch (AARCH64_DEBUG_ARCH (dreg_state.dbg_info)))
>
> and
>
> if (ptrace (PTRACE_GETREGSET, tid, NT_ARM_HW_BREAK, &iov) == 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.
I've field a bug report and included the fix for the TCL error:
https://sourceware.org/bugzilla/show_bug.cgi?id=30340
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-04-12 20:59 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 11:39 [Bug tdep/29423] New: " vries at gcc dot gnu.org
2022-07-28 11:39 ` [Bug tdep/29423] " vries at gcc dot gnu.org
2022-07-28 11:50 ` vries at gcc dot gnu.org
2022-07-28 12:24 ` vries at gcc dot gnu.org
2022-07-28 12:36 ` luis.machado at arm dot com
2022-07-28 12:41 ` vries at gcc dot gnu.org
2022-07-28 12:47 ` luis.machado at arm dot com
2022-07-28 14:15 ` vries at gcc dot gnu.org
2022-07-28 15:25 ` vries at gcc dot gnu.org
2022-07-28 15:26 ` vries at gcc dot gnu.org
2022-07-29 14:23 ` vries at gcc dot gnu.org
2023-04-11 16:51 ` ahajkova at redhat dot com
2023-04-11 16:52 ` ahajkova at redhat dot com
2023-04-11 22:07 ` luis.machado at arm dot com
2023-04-12 7:51 ` ahajkova at redhat dot com
2023-04-12 8:27 ` luis.machado at arm dot com
2023-04-12 8:27 ` luis.machado at arm dot com
2023-04-12 8:31 ` luis.machado at arm dot com
2023-04-12 12:55 ` ahajkova at redhat dot com
2023-04-12 13:12 ` luis.machado at arm dot com
2023-04-12 13:54 ` luis.machado at arm dot com
2023-04-12 17:12 ` tromey at sourceware dot org
2023-04-12 17:54 ` luis.machado at arm dot com
2023-04-12 20:59 ` ahajkova at redhat dot com [this message]
2024-01-05 15:08 ` vries at gcc dot gnu.org
2024-02-20 20:55 ` vries at gcc dot gnu.org
2024-03-14 10:24 ` cvs-commit at gcc dot gnu.org
2024-03-14 10: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-29423-4717-rGgKtMT7wp@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).