On Thu, 2010-03-25 at 19:35 -0400, David Malcolm wrote:
> (b) the critically important frame information within the heart of the
> bytecode excution loop ought to tell us what code we're running, but is
> showing up in gdb as "optimized out". (specifically, the "f" parameter
> to function PyEval_
https://fedoraproject.org/wiki/Features/EasierPythonDebugging
is currently marked as 95%, but a better answer is "it's complicated".
I've done all I can for now to finish it, and it does provide some
useful improvements, but it's being heavily impacted by a bug outside of
my expertise (see (b) bel
