1 Jul
2004
1 Jul
'04
9:57 a.m.
Helmut Eller e9626484@stud3.tuwien.ac.at writes:
Alain.Picard@memetrics.com writes:
Any clues? This is a CVS from Thu Jul 1 2004.
The problem was that the a condition was signalled when the debugger tried to produce the backtrace (the condition is usually handled); with *break-on-signals* to the debugger was invoked recursively and producing the backtrace signalled a condition ...
Should be fixed now. The workaround was to bind *break-on-signals* before getting the backtrace. We probably should do that in some more places.
Great! As a side-effect, this also fixed the bug that I reported on June 25th with the subject line "LispWorks debugger bug". Two bugs fixed for the price of one!
- Bill