[Top][All Lists]

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

Top-Level Debug/Backtrace Bug

From: Crowder, Brian
Subject: Top-Level Debug/Backtrace Bug
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

In unknown file:
   ?: 0* [primitive-load "test.scm"]
   ?: 1* here

<unnamed port>: In expression here:
<unnamed port>: Unbound variable: here


echo \(error here\) > test.scm
guile --debug -l test.scm

Yields more appropriate output:

In unknown file:
   ?: 0* [primitive-load "test.scm"]
In test.scm:
   1: 1* [error ...

test.scm:1:1: While evaluating arguments to error in expression (error
test.scm:1:1: Unbound variable: here

So this seems to work correctly.  I notice the primitive-load is still in an
unknown file on an unknown line, but this makes sense as it is being run
from C-code due to the -l command line argument.

Thanks in advance for your time,

Brian T. Crowder
Server Developer
Sony Online Entertainment

reply via email to

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