From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id C51BF3849AFA; Fri, 19 Apr 2024 06:28:24 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C51BF3849AFA DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1713508104; bh=DH5+UN8gzmdar4oZ6i0VVKnpv/qrtr16j4sg1441XnQ=; h=From:To:Subject:Date:In-Reply-To:References:From; b=uCkEYaSF1mp4iVcSumrBZX80b/YA9C8SUc+amUm2n9xl7+jiLhpW/PDZOWdIwxBV0 jH9LxV05pumCz27C2XEETkVQ7s+fTAU0Xm/H5BlFZb1x6UKRMm46aEcM02Lpt6vw1T WR1KZn0Bn/b1NQUx6FSt7kHX4jil+GaStPmbihDk= From: "thiago.bauermann at linaro dot org" To: gdb-prs@sourceware.org Subject: [Bug testsuite/31484] [gdb/testsuite] Add memcpy, memmove, memset watchpoint tests Date: Fri, 19 Apr 2024 06:28:24 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: testsuite X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: thiago.bauermann at linaro dot org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D31484 --- Comment #6 from Thiago Jung Bauermann --- Hello, Sorry for the delay in reporting back here. I agree with Tom that it makes sense to keep this PR for the testcases, as they aren't really AArch64-spec= ific and could uncover needed support in GDB for other architectures as well. I created a very simple test program and ran it under GDB with glibc 2.39 = =E2=80=94 which introduces the MOPS variants for memset, memcpy and memmove =E2=80=94= on both QEMU with -mcpu max and also on the Arm FVP emulator. GDB behaved pretty normally regarding watchpoints triggered by memcpy, memmove and memset, stopping where it's supposed to. This is because both emulators report the exact address of the watchpoint as the data trap address, so GDB has no problem identifying which watchpoint w= as triggered. Real hardware is allowed by the spec to be less precise, so unfortunately my experiment may not be representative of GDB behaviour ther= e. I'm finishing the last touches on the patch introducing the testcase, and w= ill post it on the mailing list tomorrow. I'll open a separate PR for AArch64-specific MOPS support, because in the n= ext few days I'll send a couple of patches that are needed there: one for decod= ing the new instructions for reverse execution, and one to treat a sequence of = MOPS instructions as atomic, to prevent GDB from breaking or stepping in the mid= dle of the sequence. Does that sound OK? --=20 You are receiving this mail because: You are on the CC list for the bug.=