Pablo Galindo Salgado <pablog...@gmail.com> added the comment: > It seems like ceval.c:1600 upsets the sanitizer, at least for gcc.
Even if you don't trust the sanitizer, you can also use valgrind, it shows the same error: ❯ valgrind ./python -m test test_lib2to3 ==27010== Memcheck, a memory error detector ==27010== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==27010== Using Valgrind-3.17.0 and LibVEX; rerun with -h for copyright info ==27010== Command: ./python -m test test_lib2to3 ==27010== 0:00:00 load avg: 1.53 Run tests sequentially 0:00:00 load avg: 1.53 [1/1] test_lib2to3 ==27010== Invalid read of size 8 ==27010== at 0x2363E1: _PyEval_EvalFrameDefault (ceval.c:3549) ==27010== by 0x23B270: _PyEval_EvalFrame (pycore_ceval.h:46) For running valgrind, make sure do disable pymalloc: export PYTHONMALLOC=malloc ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue44363> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
