From: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/2] Add testcase for libc memory operations
Date: Sat, 20 Apr 2024 18:33:05 -0300 [thread overview]
Message-ID: <20240420213307.976401-1-thiago.bauermann@linaro.org> (raw)
Hello,
In PR testsuite/31484, Tom de Vries suggests adding testcases that
excercise memset/memcpy/memmove and set watchpoints.
Patch 2 adds such testcase. See its description for a bit more on the
motivation. Patch 1 factors out code to check whether libc debug info is
available, which is needed for the new testcase.
Thiago Jung Bauermann (2):
gdb/testsuite: Add libc_has_debug_info require helper
gdb/testsuite: Add gdb.base/memops-watchpoint.exp
gdb/testsuite/gdb.base/memops-watchpoint.c | 40 ++++++++++
gdb/testsuite/gdb.base/memops-watchpoint.exp | 83 ++++++++++++++++++++
gdb/testsuite/gdb.base/relativedebug.exp | 13 +--
gdb/testsuite/lib/gdb.exp | 54 +++++++++++++
4 files changed, 178 insertions(+), 12 deletions(-)
create mode 100644 gdb/testsuite/gdb.base/memops-watchpoint.c
create mode 100644 gdb/testsuite/gdb.base/memops-watchpoint.exp
base-commit: 20eee7540b9f2615f7661393756fec0bb62a1495
next reply other threads:[~2024-04-20 21:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-20 21:33 Thiago Jung Bauermann [this message]
2024-04-20 21:33 ` [PATCH 1/2] gdb/testsuite: Add libc_has_debug_info require helper Thiago Jung Bauermann
2024-04-21 20:44 ` Kevin Buettner
2024-04-21 21:02 ` Kevin Buettner
2024-04-22 0:05 ` Thiago Jung Bauermann
2024-04-20 21:33 ` [PATCH 2/2] gdb/testsuite: Add gdb.base/memops-watchpoint.exp Thiago Jung Bauermann
2024-04-21 21:20 ` Kevin Buettner
2024-04-22 0:24 ` Thiago Jung Bauermann
2024-04-22 18:40 ` Kevin Buettner
2024-04-23 1:20 ` Thiago Jung Bauermann
2024-04-22 23:04 ` 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=20240420213307.976401-1-thiago.bauermann@linaro.org \
--to=thiago.bauermann@linaro.org \
--cc=gdb-patches@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