STINNER Victor <victor.stin...@haypocalc.com> 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 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. ---------- title: test_gdb - "(unable to read python frame information)" mismatch -> test_gdb, gdb/libpython.py: Unable to read information on python frame _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue8482> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
