From: Florian Weimer <fweimer@redhat.com>
To: Andrew Pinski <pinskia@gmail.com>
Cc: gdb@sourceware.org, Dmitry Belyavskiy <dbelyavs@redhat.com>
Subject: Re: Hardware watchpoints on GNU/Linux AArch64
Date: Mon, 02 Jan 2023 18:44:05 +0100 [thread overview]
Message-ID: <87zgb0ltlm.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CA+=Sn1mH08=+-589ZJpfprekgwO1S-i+ouBv6a=WB3g_0bR+0A@mail.gmail.com> (Andrew Pinski's message of "Mon, 2 Jan 2023 09:28:21 -0800")
* Andrew Pinski:
> On Mon, Jan 2, 2023 at 8:49 AM Florian Weimer via Gdb
> <gdb@sourceware.org> wrote:
>>
>> Running
>>
>> gdb-12.1-10.fc38.aarch64
>> kernel-6.2.0-0.rc1.20221230gitbff687b3dad6.15.fc38.aarch64
>>
>> I do not seem to be able to use hardware watchpoints. GDB just logs
>> warnings:
>>
>> warning: Unable to determine the number of hardware watchpoints available.
>> warning: Unable to determine the number of hardware breakpoints available.
>
> This shows up when the ptrace either fails or ptrace returns an
> unknown value for AARCH64_DEBUG_ARCH value.
> In the boot log there should be a message saying how many HW
> breakpoint and watchpoints there are and what version of the debug
> arch is there.
I only see this in the kernel log:
hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
Nothing else in the vicinity.
Thanks,
Florian
next prev parent reply other threads:[~2023-01-02 17:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-02 16:48 Florian Weimer
2023-01-02 17:08 ` Andreas Schwab
2023-01-02 17:22 ` Florian Weimer
2023-01-02 17:28 ` Andrew Pinski
2023-01-02 17:39 ` Andrew Pinski
2023-01-02 18:10 ` Andrew Pinski
2023-01-02 17:44 ` Florian Weimer [this message]
2023-01-02 17:59 ` Florian Weimer
2023-01-05 14:17 ` Luis Machado
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=87zgb0ltlm.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=dbelyavs@redhat.com \
--cc=gdb@sourceware.org \
--cc=pinskia@gmail.com \
/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).