guile-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: No way out.


From: Han-Wen Nienhuys
Subject: Re: No way out.
Date: Sat, 31 Dec 2005 16:09:53 +0100
User-agent: Mozilla Thunderbird 1.0.7-1.1.fc4 (X11/20050929)

Neil Jerram wrote:
Han-Wen Nienhuys <address@hidden> 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 - address@hidden - http://www.xs4all.nl/~hanwen




reply via email to

[Prev in Thread] Current Thread [Next in Thread]