[Top][All Lists]

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

Re: Top-Level Debug/Backtrace Bug

From: Martin Grabmueller
Subject: Re: Top-Level Debug/Backtrace Bug
Date: Fri, 5 Oct 2001 17:15:44 +0200 (MEST)

> From: "Crowder, Brian" <address@hidden>
> Date: Wed, 3 Oct 2001 16:48:56 -0700
> It seems like erroneous code at the top-level of an .scm file fails to yield
> filenames and line-numbers for backtrace/error display.  For example:
> echo error here > test.scm
> guile --debug -l test.scm
> Yields something like
> Backtrace:
> In unknown file:
>    ?: 0* [primitive-load "test.scm"]
>    ?: 1* here
> <unnamed port>: In expression here:
> <unnamed port>: Unbound variable: here

The reason is that the Guile reader only records source positions for
cons cells.  That means that a symbol like `here' will not have any
source location attached, whereas a quotation like `'here' will.


reply via email to

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