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 D59843858032; Fri, 28 Jul 2023 12:19:00 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D59843858032
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1690546740;
	bh=B8LnAVJf9LMj8LIXhtPooI1MRBLj8id/7H+VO6Db/oQ=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=Odfz4IGZemMvnuFYwMJBAXooVKsR9QtpfbIDkdA+j0mD2WxlNJddqzHyRhfYUJr/k
	 oYPHe77MgrW6aN54g+2jZkY2hPpFdb1KiIldNg5MIgIOcDymJeqUiBvVlmpEpYecnK
	 v2gLwDqxr6V4MOICspZ63y5ol3zmVJj4lJYv5eqk=
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug dap/30686] [gdb/dap] ERROR: eof reading json header in
 gdb.dap/cond-bp.exp
Date: Fri, 28 Jul 2023 12:18:59 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: dap
X-Bugzilla-Version: HEAD
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: tromey at sourceware dot org
X-Bugzilla-Target-Milestone: 14.1
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-30686-4717-41Z7aUWrJP@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-30686-4717@http.sourceware.org/bugzilla/>
References: <bug-30686-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=3D30686

--- Comment #8 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gn=
u.org> ---
The master branch has been updated by Tom Tromey <tromey@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D0c8a0b88d18d=
9c8d6cd52bd1a56d6ab88570f287

commit 0c8a0b88d18d9c8d6cd52bd1a56d6ab88570f287
Author: Tom Tromey <tromey@adacore.com>
Date:   Thu Jul 27 07:54:18 2023 -0600

    Re-acquire GIL earlier in gdbpy_parse_and_eval

    Tom de Vries filed a bug about an intermittent gdb DAP failure -- and
    coincidentally, at the same time, Alexandra H=C3=A1jkov=C3=A1 sent emai=
l about a
    somewhat similar failure.

    After looking into this for a while (with no results) using ASan and
    valgrind, I found that setting PYTHONMALLOC=3Dmalloc_debug found the bug
    instantly.

    The problem is that gdbpy_parse_and_eval releases the GIL while
    calling parse_and_eval, but fails to re-acquire it before calling
    value_to_value_object.  This is easily fixed by introducing a new
    scope.

    I wonder whether the test suite should unconditionally set
    PYTHONMALLOC=3Dmalloc_debug.

    Tested-by: Tom de Vries <tdevries@suse.de>
    Reviewed-By: Tom de Vries <tdevries@suse.de>
    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=3D30686

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