more informative stack traces

[Erik Max Francis]

"L.C." wrote:

> I am proposing a different style of stack trace which I found more
> useful in debugging problems with live code. The main change involves
> showing the actual parameter values in function calls, gdb-style.
> It sounds simple because it really is, but it saves lots of guesswork
> when navigating through the stack to see what caused a problem.

Looks pretty neat.  I find myself wondering what the arguments were in
the call stack myself.

-- 
 Erik Max Francis / max at alcyone.com / http://www.alcyone.com/max/
 __ San Jose, CA, USA / 37 20 N 121 53 W / &tSftDotIotE
/  \ The hour which gives us life begins to take it away.
\__/ Seneca
    Church / http://www.alcyone.com/pyos/church/
 A lambda calculus explorer in Python.