[Bug dap/30686] [gdb/dap] ERROR: eof reading json header in gdb.dap/cond-bp.exp

["cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>]

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

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

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

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ájková sent email about a
    somewhat similar failure.

    After looking into this for a while (with no results) using ASan and
    valgrind, I found that setting PYTHONMALLOC=malloc_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=malloc_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=30686

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