public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "brobecker at gnat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/31484] [gdb/testsuite] Add memcpy, memmove, memset watchpoint tests
Date: Sat, 30 Mar 2024 03:38:07 +0000 [thread overview]
Message-ID: <bug-31484-4717-gzFPbQclqr@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31484-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=31484
Joel Brobecker <brobecker at gnat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |brobecker at gnat dot com
--- Comment #3 from Joel Brobecker <brobecker at gnat dot com> ---
Hello,
What do you guys think of renaming this PR to implementing the missing
features, and then adding the testcases can be part of the implementation?
That way, the implementation of the features can be tracked via this PR.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2024-03-30 3:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-14 11:14 [Bug testsuite/31484] New: " vries at gcc dot gnu.org
2024-03-14 11:14 ` [Bug testsuite/31484] " vries at gcc dot gnu.org
2024-03-14 11:23 ` luis.machado at arm dot com
2024-03-23 4:29 ` thiago.bauermann at linaro dot org
2024-03-30 3:38 ` brobecker at gnat dot com [this message]
2024-03-30 7:48 ` vries at gcc dot gnu.org
2024-04-02 9:53 ` luis.machado at arm dot com
2024-04-19 6:28 ` thiago.bauermann at linaro dot org
2024-04-20 18:42 ` brobecker at gnat dot com
2024-04-22 4:17 ` thiago.bauermann at linaro dot org
2024-04-22 4:33 ` thiago.bauermann at linaro dot org
2024-04-22 23:09 ` thiago.bauermann at linaro dot org
2024-04-30 3:03 ` cvs-commit at gcc dot gnu.org
2024-04-30 3:58 ` thiago.bauermann at linaro dot org
2024-04-30 9:46 ` luis.machado at arm dot com
2024-04-30 10:08 ` 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-31484-4717-gzFPbQclqr@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).