interpreter crashes

Barry A. Warsaw barry at
Mon Oct 29 07:42:31 CET 2001

>>>>> "PR" == Paul Rubin <phr-n2001d at> writes:

    PR> The backtraces aren't very informative.  The evaluator is
    PR> crashing, almost certainly due to data corruption having
    PR> happened sometime earlier.  But sure, I'll include them.

Try running your program under gdb.  Often, nonsense stack traces are
caused by memory corruptions which can be caught much sooner under
gdb, producing more usable stack traces.


More information about the Python-list mailing list