But what I wanted to point out (not very constructively - sorry) was that it would be nice if debug.assertTrue printed out what it tried to assert as a message, to the console, so that one could diagnose a little without having to find the line in the source code.

I've been hitting a number of these. Often they happen at odd times, with very little to go on to even start debugging - say when compiling a function. There isn't a stack trace that's informative, I don't know what abcl was doing, and the report doesn't give me enough information to start.

A lot of the time I'll spend the effort to try to track it down, but I'd certainly appreciate it if some of the developers could think a bit about how to improve the situation wrt debugging such.

Regards,

Alan

On Thu, May 6, 2010 at 4:16 AM, Mark Evenson <evenson@panix.com> wrote:

On 5/4/10 4:47 PM, Alan Ruttenberg wrote:
> Blood pressure, specifically.
>
> What does one do with this:
>
> ABCL Debug.assertTrue() assertion failed!
> java.lang.Error: ABCL Debug.assertTrue() assertion failed!
> at org.armedbear.lisp.Debug.assertTrue(Debug.java:46)
> at org.armedbear.lisp.Package.shadowingImport(Package.java:601)
> at org.armedbear.lisp.PackageFunctions$9.execute(PackageFunctions.java:190)
> at org.armedbear.lisp.Primitive.execute(Primitive.java:108)
> at org.armedbear.lisp.Symbol.execute(Symbol.java:776)
>
> No message - go hunt in source code. Yuck.

Provide a test case please? But you knew that…

No recent work should have impacted this section of the code from what I
can make of it, so we need to know how this code is failing to fix it.

--
"A screaming comes across the sky. It has happened before, but there
is nothing to compare to it now."

_______________________________________________
armedbear-devel mailing list
armedbear-devel@common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel