Neil Jerram wrote:
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
Backtraces haven't been appearing since I started using 1.7, for over a year
Because of my interest in Guile's debugging infrastructure, I'd like
to understand and fix this. Your statement is a bit vague, though,
unless you mean _only_ the following.
See also,
http://lists.gnu.org/archive/html/guile-devel/2005-05/msg00010.html
As http://lists.gnu.org/archive/html/guile-devel/2005-05/msg00019.html
already asked (and to which there appears to be no reply), were you
running with the debugging evaluator (in other words (debug-enable
'debug))? If not, does it help to say (debug-enable 'debug) as well
as (debug-enable 'backtrace)?
No it doesn't. I have
;;; General settings
;;; debugging evaluator is slower. This should
;;; have a more sensible default.
(if (ly:get-option 'verbose)
(begin
(debug-enable 'debug)
(debug-enable 'backtrace)
(read-enable 'positions)))
near the top of the first .scm file, but lilypond --verbose doesn't
produce any backtraces.
If you intend to look at this, then I can try to isolate it to a smaller
case.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
