From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
	id A4846395A450; Mon, 12 Dec 2022 09:46:55 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A4846395A450
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1670838415;
	bh=PljpDhQazNLIz1ggEk6qsoAK+sU9hKlUnMITSDa0AAo=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=eIkbhlRvc3Yg2XmHzGtrehpSOWnSX81caXoQ3gvLxMlIKgvoRAD94oZ1D0Un7LzD9
	 tXUYvxjFp9tbUStps/WwgchD4XvFLgOgv8dBREb7VJcnxp52JRd3zapdTMVGPaMAo6
	 aV6q3YKS07/xPecdL0H4QuFgVdYBlB3J/kb0L23c=
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tdep/29868] [gdb/tdep, s390x] breakpoint.c:5784:
 internal-error: bpstat_stop_status_nowatch: Assertion
 `!target_stopped_by_watchpoint ()'
Date: Mon, 12 Dec 2022 09:46:54 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: tdep
X-Bugzilla-Version: HEAD
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.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: <bug-29868-4717-tCytYy7jPs@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-29868-4717@http.sourceware.org/bugzilla/>
References: <bug-29868-4717@http.sourceware.org/bugzilla/>
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: <gdb-prs.sourceware.org>

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

--- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #2)
> we try to clear the watch point status in
> s390_linux_nat_target::stopped_by_watchpoint to make sure that we "Do not
> report this watchpoint again".  That doesn't seem to have any effect thou=
gh,

And that seems to be documented behaviour, in ./arch/s390/kernel/ptrace.c, =
in
__poke_user_per we have:
...
        /*=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
         * There are only three fields in the per_info struct that the=20=
=20=20=20=20=20=20=20=20=20
         * debugger user can write to.=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20
         * 1) cr9: the debugger wants to set a new PER event mask=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20
         * 2) starting_addr: the debugger wants to set a new starting=20=20=
=20=20=20=20=20=20=20=20=20
         *    address to use with the PER event mask.=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
         * 3) ending_addr: the debugger wants to set a new ending=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20
         *    address to use with the PER event mask.=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
         * The user specified PER event mask and the start and end=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20
         * addresses are used only if single stepping is not in effect.=20=
=20=20=20=20=20=20=20=20
         * Writes to any other field in per_info are ignored.=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
         */
...

So, the bits that we're trying to clear here in per_struct.lowcore, after t=
he
fields listed above.

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