[Top][All Lists]

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

Re: Backtraces in Guile 2.0

From: Mike Gran
Subject: Re: Backtraces in Guile 2.0
Date: Tue, 22 Feb 2011 09:53:56 -0800 (PST)

> From:Andy Wingo <address@hidden>
> In any case it seems that symbol1.scm.go tail-calls symbol->string, so
> we are left without source info.  Bummer.  We could improve this by
> keeping a ring buffer of previous frames, like JRM suggests in

So, the specific line on which the error occurred will always read
"in unknown file" because source data is a property of procedures.  And,
when procedure A tail-calls procedure B, the backtrace may only
display the information of the procedure A.  Right?

Thus, if I understand correctly, the closest I can get to getting source
info for this trivial case would be to change the script to

  (symbol->string "HELLO")

Adding a #t so it can't be tail-called.  Then I get

In unknown file:
   ?: 2 [load-compiled/vm 
In /home/Mike/tmp.scm:
   1: 1 [#<procedure 13fa550 ()>]
In unknown file:
   ?: 0 [symbol->string "STRING"]
ERROR: In procedure symbol->string:



reply via email to

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