From: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
To: Luis Machado <luis.machado@arm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2 2/2] gdb/testsuite: Add gdb.base/memops-watchpoint.exp
Date: Mon, 22 Apr 2024 13:07:25 -0300 [thread overview]
Message-ID: <87r0ex2xfm.fsf@linaro.org> (raw)
In-Reply-To: <c6697542-2850-4152-a47e-4e2ac4d85d90@arm.com> (Luis Machado's message of "Mon, 22 Apr 2024 15:39:06 +0100")
Hello Luis,
Thanks for reviewing the patches!
Luis Machado <luis.machado@arm.com> writes:
> On 4/21/24 23:26, Thiago Jung Bauermann wrote:
>> +setup_kfail breakpoints/31665 arm*-*-linux*
>> +gdb_test "continue" \
>> + [multi_line \
>> + "Continuing\\." \
>> + "" \
>> + "(Hardware w|W)atchpoint ${decimal}: -location a\\\[28\\\]" \
>> + "" \
>> + "Old value = 104 'h'" \
>> + "New value = 0 '\\\\000'" \
>> + ".*memset.* \\(\\) at .*:$decimal" \
>> + ".*"] \
>> + "continue until memset watchpoint hits"
>> +
>> +setup_kfail breakpoints/31665 arm*-*-linux*
>> +gdb_test "continue" \
>> + [multi_line \
>> + "Continuing\\." \
>> + "" \
>> + "(Hardware w|W)atchpoint ${decimal}: -location b\\\[28\\\]" \
>> + "" \
>> + "Old value = 101 'e'" \
>> + "New value = 114 'r'" \
>> + ".*memcpy.* \\(\\) at .*:$decimal" \
>> + ".*"] \
>> + "continue until memcpy watchpoint hits"
>> +
>> +# Note: Some architectures use memcpy for memmove.
>> +setup_kfail breakpoints/31665 arm*-*-linux*
>> +gdb_test "continue" \
>> + [multi_line \
>> + "Continuing\\." \
>> + "" \
>> + "(Hardware w|W)atchpoint ${decimal}: -location c\\\[28\\\]" \
>> + "" \
>> + "Old value = 100 'd'" \
>> + "New value = 114 'r'" \
>> + ".*(memmove|memcpy).* \\(\\) at .*:$decimal" \
>> + ".*"] \
>> + "continue until memmove watchpoint hits"
>
> For this test, on aarch64 I see full passes, but on 32-bit Arm I see
> 3 passes and 3 kfail's.
>
> Is that the expected outcome?
Yes, the testcase uncovered a bug in in hardware watchpoints with 32-bit
Arm (the testcase fully passes when the testcase is modified to use
software watchpoints) so I opened PR breakpoints/31665 to track it.
I didn't have the chance to investigate the problem yet, but it's in my
TODO list.
--
Thiago
prev parent reply other threads:[~2024-04-22 16:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-21 22:26 [PATCH v2 0/2] Add testcase for libc memory operations Thiago Jung Bauermann
2024-04-21 22:26 ` [PATCH v2 1/2] gdb/testsuite: Add libc_has_debug_info require helper Thiago Jung Bauermann
2024-04-21 22:26 ` [PATCH v2 2/2] gdb/testsuite: Add gdb.base/memops-watchpoint.exp Thiago Jung Bauermann
2024-04-22 14:39 ` Luis Machado
2024-04-22 16:07 ` Thiago Jung Bauermann [this message]
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=87r0ex2xfm.fsf@linaro.org \
--to=thiago.bauermann@linaro.org \
--cc=gdb-patches@sourceware.org \
--cc=luis.machado@arm.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).