[issue8482] test_gdb, gdb/libpython.py: Unable to read information on python frame

Changes by Dave Malcolm : -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue8482] test_gdb, gdb/libpython.py: Unable to read information on python frame

Dave Malcolm added the comment: > test_gdb fails (Unable to read information on python frame) on my i386 > computer (32 bits) with -O1 (but it doesn't with -O0). I'm using Debian > Sid: gcc 4.4.3 and gdb 7.1. This should be fixed now that issue 8605 is resolved: we now skip test_gdb if the com

[issue8482] test_gdb, gdb/libpython.py: Unable to read information on python frame

Changes by Ezio Melotti : -- nosy: +ezio.melotti ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue8482] test_gdb, gdb/libpython.py: Unable to read information on python frame

STINNER Victor added the comment: > the issue is that on 64-bit gcc builds with enough optimization, > the argument "PyFrameObject *f" is passed as a register, > and that gets clobbered at various locations within the > implementation of PyEval_EvalFrameEx. test_gdb fails (Unable to read info