Andy Wingo 65bce23759 breakpoints from recursive prompts work ... * module/system/vm/traps.scm (new-disabled-trap): Don't manipulate the VM trace level in the enable and disable handlers. Unfortunately, this makes traps not work unless you enable hooks, but given that vm_dispatch_hook has to set trace-level to 0, there needs to be an object with a broader view of what traps are enabled. That object is the hook state. * module/system/vm/trap-state.scm (trap-state->trace-level): New procedure. (with-default-trap-handler): Add an optional trap-state argument. Now makes sure that the vm-trace-level is set appropriately during the execution of the thunk, allowing for breakpoints from recursive prompts.		2010-09-21 21:37:11 +02:00
..
coverage.scm	Add (system vm coverage).	2010-05-07 13:47:53 +02:00
frame.scm	Remove unneeded #:use-module.	2010-08-27 18:59:42 +02:00
inspect.scm	add a silly inspector	2010-01-12 00:18:24 +01:00
instruction.scm	rename libguile to libguile-@EFFECTIVE_VERSION@, currently libguile-2.0	2010-03-16 21:20:34 +01:00
objcode.scm	rename libguile to libguile-@EFFECTIVE_VERSION@, currently libguile-2.0	2010-03-16 21:20:34 +01:00
program.scm	Add program-free-variables' to (system vm program)'.	2010-05-07 13:47:52 +02:00
trace.scm	instruction tracing tweak	2010-09-16 13:04:57 +02:00
trap-state.scm	breakpoints from recursive prompts work	2010-09-21 21:37:11 +02:00
traps.scm	breakpoints from recursive prompts work	2010-09-21 21:37:11 +02:00
vm.scm	add vm-abort-continuation-hook, vm-restore-continuation-hook	2010-09-16 12:48:41 +02:00