public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/31484] [gdb/testsuite] Add memcpy, memmove, memset watchpoint tests
Date: Tue, 30 Apr 2024 03:03:49 +0000	[thread overview]
Message-ID: <bug-31484-4717-qzIbsHYaLV@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 #11 from Sourceware Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Thiago Bauermann
<bauermann@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=6b4b601b35a0aaf2b8b5db8e5793302736504171

commit 6b4b601b35a0aaf2b8b5db8e5793302736504171
Author: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
Date:   Thu Apr 18 23:24:55 2024 -0300

    gdb/testsuite: Add gdb.base/memops-watchpoint.exp

    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

    Approved-by: Kevin Buettner <kevinb@redhat.com>

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

  parent reply	other threads:[~2024-04-30  3:03 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
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 [this message]
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-qzIbsHYaLV@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).