[issue8482] test_gdb - "(unable to read python frame information)" mismatch

Nick Coghlan added the comment: Thanks, I understood your summary significantly better than I did the bug discussion :) Any of your 3 options sounds reasonable to me (although i. sounds potentially fragile in the face of different versions of gcc, so iii. might be necessary anyway). The qui

[issue8482] test_gdb - "(unable to read python frame information)" mismatch

Dave Malcolm added the comment: See https://bugzilla.redhat.com/show_bug.cgi?id=556975#c21 I'll try to summarize: as I understand things, 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 variou

[issue8482] test_gdb - "(unable to read python frame information)" mismatch

STINNER Victor added the comment: test_gdb of py3k now pass with ./configure --with-pydebug (no optimization <=> -O0), but fail (Unable to read information on python frame) with ./configure (-O3). The test does also fail with -O1. Recompile only ceval.c with -O0 is enough to fix this issue: -

[issue8482] test_gdb - "(unable to read python frame information)" mismatch

Changes by Martin v. Löwis : -- assignee: -> dmalcolm ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://ma

[issue8482] test_gdb - "(unable to read python frame information)" mismatch

Nick Coghlan added the comment: I'll wait for Dave to weigh in before I dig any further - the problem I am seeing seems to have a lot in common with the issue he reported on 64-bit Fedora, but I only followed about half of that bug discussion. -- _

[issue8482] test_gdb - "(unable to read python frame information)" mismatch

Changes by Nick Coghlan : -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/opti

[issue8482] test_gdb - "(unable to read python frame information)" mismatch

Nick Coghlan added the comment: I'll weight for Dave to weigh in before I dig any further - the problem I am seeing seems to have a lot in common with the issue he reported on 64-bit Fedora, but I only followed about half of that bug discussion. -- ___

[issue8482] test_gdb - "(unable to read python frame information)" mismatch

STINNER Victor added the comment: > The test actually runs fine under "./configure --with-pydebug" (...) I changed configure to disable all compiler optimisations if --with-pydebug is used. Retry with ./configure CFLAGS="-O0". A variable may be optimized (use a register instead a variable all

[issue8482] test_gdb - "(unable to read python frame information)" mismatch

Nick Coghlan added the comment: Thanks Victor. The test actually runs fine under "./configure --with-pydebug", but reverting to a plain "./configure" and rebuilding means I get the error again. Definitely sounds like it could be due to the compiler failing to make some relevant info availabl

[issue8482] test_gdb - "(unable to read python frame information)" mismatch

STINNER Victor added the comment: Readable version of the error message (with newlines): - AssertionError: 'Breakpoint 1 at 0x453510: file Objects/object.c, line 330. [Thread debugging using libthread_db enabled] Breakpoint 1, PyObject_Print (op=42, fp=0x77532780, flags=1) at Ob

[issue8482] test_gdb - "(unable to read python frame information)" mismatch

Nick Coghlan added the comment: Potentially relevant gcc and gdb version info: ~$ gcc --version gcc (Ubuntu 4.4.1-4ubuntu9) 4.4.1 Copyright (C) 2009 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY

[issue8482] test_gdb - "(unable to read python frame information)" mismatch

Nick Coghlan added the comment: And Dave's comment from the other issue: Reading the frame information seems to be highly sensitive to the optimization level and the exact version of gcc for the build, and the exact version of gdb, alas. I've been tracking a failure like the one you describe

[issue8482] test_gdb - "(unable to read python frame information)" mismatch

New submission from Nick Coghlan : Remaining failure after resolution of issue8437: == FAIL: test_basic_command (test.test_gdb.PyBtTests) Verify that the "py-bt" command works