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, 20 Apr 2024 18:42:01 +0000	[thread overview]
Message-ID: <bug-31484-4717-OQCSWJLFsm@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31484-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=31484

--- Comment #7 from Joel Brobecker <brobecker at gnat dot com> ---
> Does that sound OK?

Sounds good to me, Thiago. If you wouldn't mind, can you post here the URL of
the new PR? And it would be useful also in the other PR if you posted the URL
of the patch series once posted on gdb-patches. I try to locate them through
the PR number, but sometimes I miss things in my searches...

Thank you!

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2024-04-20 18:42 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
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 [this message]
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-OQCSWJLFsm@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).