Hi, Andy Wingo <[email protected]> writes:
> I would prefer not to enshrine a "regular / debug" split again though. I > guess that's what really bothers me. It's especially egregious if you > can't switch at runtime. The split survived! :-) --8<---------------cut here---------------start------------->8--- $ guile -c 'sdf' ERROR: In procedure catch-closure: ERROR: Unbound variable: sdf $ guile --debug -c 'sdf' Backtrace: In ice-9/boot-9.scm: 170: 8 [catch #t #<catch-closure d5a660> ...] In unknown file: ?: 7 [catch-closure] In ice-9/boot-9.scm: 62: 6 [call-with-prompt prompt0 ...] In module/ice-9/eval.scm: 389: 5 [eval # #] In unknown file: ?: 4 [eval-string "sdf" #<undefined>] In module/ice-9/eval.scm: 356: 3 [eval #<memoized sdf> ()] In unknown file: ?: 2 [memoize-variable-access! #<memoized sdf> #<directory (guile-user) b60120>] In ice-9/boot-9.scm: 115: 1 [#<procedure dd08c0 at ice-9/boot-9.scm:109:6 (thrown-k . args)> unbound-variable ...] In unknown file: ?: 0 [catch-closure unbound-variable #f "Unbound variable: ~S" (sdf) #f] ERROR: In procedure catch-closure: ERROR: Unbound variable: sdf $ guile --version guile (GNU Guile) 1.9.11.176-1b912 --8<---------------cut here---------------end--------------->8--- Don’t get me wrong, this is not to say that we should make the split even more acute! I actually think that disabling automatic backtraces is much more visible that disabling VM hooks. What do you think? Thanks, Ludo’.
