[Top][All Lists]

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

Re: [Gcl-devel] load-time value support, closed compile bugs in ANSItest

From: Paul F. Dietz
Subject: Re: [Gcl-devel] load-time value support, closed compile bugs in ANSItest suite
Date: Tue, 23 Nov 2004 20:51:56 -0600
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040803

Mike Thomas wrote:
Hi Paul.

| I'm seeing this (built with --enable-ansi on a Redhat 9 x86 machine
| this morning), then doing (load "gclload.lsp") in a running lisp:

Thanks very much for this feedback, it is very helpful.

A quick eyeball shows that RATIONAL.1, some PATHNAME and DIRECTORY tests and
most importantly, every OPEN.* test failed on Windows.

I was looking at the swathe of open test failures last night and found that
the test forms I tried all actually worked if just entered at a GCL prompt.
In the test log they are failing like this:


Expected value: "abcdefghij"

despite being OK at the command prompt.

OPEN.2 gives:

Expected value: "abcdefghij"


Expected value: "abcdefghij"

That is, the eroor number increases by one each time??  I'll follow up as
time permits - will have to find out what internal-simple-errors are first.

The RT system normally catches errors and indicates them by printing
them with *print-readably* bound to NIL (that number is probably
just some counter to distinguish different condition objects).

You can let the signal through (so the test enters the debugger) by
binding RT:*CATCH-ERRORS* to NIL.  This should print more information
about the error to help you diagnose the cause.


reply via email to

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