This is the mail archive of the guile@cygnus.com mailing list for the guile project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: Profiling & tracing & questions.


Mikael Djurfeldt <mdj@nada.kth.se> writes:

 > hjstein@bfr.co.il (Harvey J. Stein) writes:
 > >
 > > Why is it that apply-frame-handler & exit-frame-handler only seem to
 > > get called when a procedure's property list has a value of #t for the
 > > trace property?
 > 
 > Non-existent documentation.
 > 
 > They are also called if the apply-frame and exit-frame traps are
 > enabled:
 > 
 >   (trap-enable 'apply-frame)
 >   (trap-enable 'exit-frame)
 > 
 > This works even if the debug-option trace isn't enabled.
 > 
 > (BTW, as with the other library option interfaces, you can get a
 >  verbose listing: Try (traps #t))

I can't seem to get it to work:

guile> (trap-enable 'exit-frame)
ERROR: In procedure evaluator-traps-interface in expression
(evaluator-traps-interface (append flags #)):
ERROR: unhandled-exception: exit-frame #<debug-object -40001028> ()
ABORT: (misc-error)

Type "(backtrace)" to get more information.
guile> (trap-enable 'apply-frame)
ERROR: In expression (evaluator-traps-interface):
ERROR: unhandled-exception: apply-frame #<debug-object -400010a8> #f
ABORT: (misc-error)
guile> (backtrace)

Backtrace:
0* [trap-enable apply-frame]
1  (evaluator-traps-interface)
2* [#<procedure (symbol define?)> evaluator-traps-interface #f]

Type "(debug-enable 'backtrace)" if you would like a backtrace
automatically if an error occurs in the future.
guile> 
-- 
Harvey J. Stein
BFM Financial Research
hjstein@bfr.co.il