[armedbear-devel] how to debug?

Alan Ruttenberg alanruttenberg at gmail.com
Tue Feb 16 16:58:31 UTC 2010


It loads without error, but gets an error when run. The error does not
occur in evaluated code. There is a compiler macro involved, but it
has worked in the past.

(define-compiler-macro regex-replace-all
    (&whole form  regex string replacement)
  "Compile constant regex to pattern at compile time"
  (cond ((stringp regex)
	 `(#"replaceAll" (#0"matcher"
			  (load-time-value
			   (#0"compile" 'java.util.regex.Pattern ,regex)) ,string)
			 ,replacement))
        (t form)))

When I don't get a loading error, I get the same error on running. I
don't understand why I get all the gensym style warnings either.
-Alan

(load "/Users/alanr/Downloads/2010-02-16/obo.abcl")
; Loading #P"/Users/alanr/Downloads/2010-02-16/obo.abcl" ...
; Loaded #P"/Users/alanr/Downloads/2010-02-16/obo.abcl" (0.079 seconds)
T
CL-USER(4): (setq obo (make-instance 'obo :path
"/Users/alanr/Downloads/2010-02-15/quality.obo.txt"))
#<OBO {A7533B}>
CL-USER(5): (read-obo obo)
Debugger invoked on condition of type JAVA-EXCEPTION:
  Java exception 'SchemeException: ERROR:
NO INSTANCE METHOD OF TYPE

  (.matcher org.armedbear.lisp.Cons ...)'.
Restarts:
  0: TOP-LEVEL Return to top level.
[1] CL-USER(6): :bt
  0: (SYSTEM:BACKTRACE)
  1: (APPLY #<FUNCTION SYSTEM:BACKTRACE {59067}> NIL)
  2: (SYSTEM:BACKTRACE)
  3: (INVOKE-DEBUGGER
 #<JAVA-EXCEPTION SchemeException: ERROR:
NO INSTANCE METHOD OF TYPE

  (.matcher org.armedbear.lisp.Cons ...) {A01AAF}>)
  4: org.armedbear.lisp.Java.jstatic(Java.java:402)
  5: org.armedbear.lisp.Java.access$600(Java.java:50)
  6: org.armedbear.lisp.Java$9.execute(Java.java:434)
  7: org.armedbear.lisp.Primitive.execute(Primitive.java:174)
[1] CL-USER(7):


On Tue, Feb 16, 2010 at 2:31 PM, Mark Evenson <evenson at panix.com> wrote:
> On 2/16/10 12:42 AM, Alan Ruttenberg wrote:
>>
>> Could this be the result of some corruption of my java environment?
>
> […]
>
> I don't think so, because in my experience Java installations fail
> catastrophically.
>
> Do you have possibly two compilers in your environment?
>
> For what it's worth, I was able to compile obo.lisp from lsw r619.  The
> compiler complained heavily about READ-OBO-KEY-VALUES OBO STREAM claiming
> that variables named LAMBDA::Gnnn "being defined but never used", but
> produced the output attached to this message.  Perhaps you can check your
> installation by attempting to load this FASL?
>
> I used ABCL svn r12481 with the OSX 10.2.0 jdk 1.6.0_17 to build.
>
> Not sure what else I can try from my side without more details, but if you
> have a suggestion, I'd be happy to try to help.
>
> --
> "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 at common-lisp.net
> http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel
>
>




More information about the armedbear-devel mailing list