From: Kevin Buettner <kevinb@redhat.com>
To: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
Cc: gdb-patches@sourceware.org, Luis Machado <luis.machado@arm.com>
Subject: Re: [PATCH v4] gdb/testsuite: Add gdb.base/memops-watchpoint.exp
Date: Thu, 25 Apr 2024 19:44:49 -0700 [thread overview]
Message-ID: <20240425194449.79797d27@f39-zbm-amd> (raw)
In-Reply-To: <20240426014626.1668298-1-thiago.bauermann@linaro.org>
On Thu, 25 Apr 2024 22:46:26 -0300
Thiago Jung Bauermann <thiago.bauermann@linaro.org> wrote:
> Test behaviour of watchpoints triggered by libc's memset/memcpy/memmove.
> These functions are frequently optimized with specialized instructions
> that favor larger memory access operations, so make sure GDB behaves
> correctly in their presence.
>
> There's a separate watched variable for each function so that the testcase
> can test whether GDB correctly identified the watchpoint that triggered.
>
> Also, the watchpoint is 28 bytes away from the beginning of the buffer
> being modified, so that large memory accesses (if present) are exercised.
>
> PR testsuite/31484
> Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=31484
> ---
>
> Changes in v4:
> - Also accept memmove symbol for memcpy watchpoint test (Suggested by Kevin).
>
> Changes in v3:
> - Reworked "continue until memset/memcpy/memmove watchpoint hits" tests to
> have a chance to work even without libc debug info (Suggested by Kevin).
> - Dropped "require libc6_has_debug_info" call (Suggested by Kevin).
>
> Changes in v2:
> - Ensure watchpoints are aligned to 4 bytes.
> - Add kfail for arm-linux.
LGTM, plus I didn't find any problems while testing on Fedora 39 x86_64,
both with and without debuginfo.
Approved-by: Kevin Buettner <kevinb@redhat.com>
next prev parent reply other threads:[~2024-04-26 2:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 1:46 Thiago Jung Bauermann
2024-04-26 2:44 ` Kevin Buettner [this message]
2024-04-30 3:08 ` Thiago Jung Bauermann
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=20240425194449.79797d27@f39-zbm-amd \
--to=kevinb@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=luis.machado@arm.com \
--cc=thiago.bauermann@linaro.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).