Once in a blue moon, I manage create a runaway process. I use -:h500000 to stop it before it eats all the memory and it stops in the debugger. Perfect!
Now here's the problem: *** ERROR IN jazz.system-exception-hook, "../jazz/lib/jazz/src/jazz/ dialect/core/exception.scm"@65.3 -- Heap overflow exc == '#<heap-overflow-exception #6> other == ##thread-end-with-uncaught-exception! 1> ,b *** ERROR IN jazz.system-exception-hook, "../jazz/lib/jazz/src/jazz/ dialect/core/exception.scm"@65.3 -- Heap overflow exc == '#<heap-overflow-exception #6> other == ##thread-end-with-uncaught-exception! 1> ,q logout
Is there a way to use the debugger, to see the runaway stack, or is it completely locked out?
Afficher les réponses par date
On 2009-10-30, at 11:03 AM, Stéphane Le Cornec wrote:
Once in a blue moon, I manage create a runaway process. I use -:h500000 to stop it before it eats all the memory and it stops in the debugger. Perfect!
Now here's the problem: *** ERROR IN jazz.system-exception-hook, "../jazz/lib/jazz/src/jazz/ dialect/core/exception.scm"@65.3 -- Heap overflow exc == '#<heap-overflow-exception #6> other == ##thread-end-with-uncaught-exception! 1> ,b *** ERROR IN jazz.system-exception-hook, "../jazz/lib/jazz/src/jazz/ dialect/core/exception.scm"@65.3 -- Heap overflow exc == '#<heap-overflow-exception #6> other == ##thread-end-with-uncaught-exception! 1> ,q logout
Is there a way to use the debugger, to see the runaway stack, or is it completely locked out?
My guess is that you don't have enough heap space to generate a backtrace (it may be very deep and each frame has some space overhead when it is printed).
One "solution" is to display each frame "manually". So do ,1 to move to frame 1 and then ,2 for frame 2 and so on.
Marc
-
Marc Feeley -
Stéphane Le Cornec