[ZODB-Dev] Latest news: core dump with small change to POSException.py

[Greg Ward]

On 25 September 2001, Jeremy Hylton said:
>   for PyEval_EvalCodeEx grab the co->co_name value (*)
>   for eval_frame grab the f->f_lineno value
> 
> That information for the top frame or two may help.

OK, here it is:

(gdb) frame 0
#0  eval_frame (f=0x810f984) at Python/ceval.c:726
726                             Py_DECREF(v);
(gdb) p f->f_lineno
$1 = 397
(gdb) frame 1
#1  0x8075400 in PyEval_EvalCodeEx (co=0x81934c0, globals=0x8198144, 
    locals=0x0, args=0x8198964, argcount=5, kws=0x8198978, kwcount=1, 
    defs=0x81ae800, defcount=2, closure=0x0) at Python/ceval.c:2542
2542            retval = eval_frame(f);
(gdb) p ((PyStringObject *)co->co_name)->ob_sval
$3 = "t"

Assuming testConflict.py is the file, line 397 is an "except" clause.  I
don't see any identifier 't' in that code.

        Greg