Hi, I'm trying ASDF-JAR again. I'm working with the svn trunk (current revision 14736). Here's what I get:
CL-USER(1): (require 'asdf) ("uiop" "UIOP" "asdf" "ASDF") CL-USER(2): (require 'abcl-contrib) Using probed value of abcl-contrib: 'NIL'. ("ABCL-CONTRIB") CL-USER(3): (require 'asdf-jar) #<THREAD "interpreter" {13AD88B}>: Debugger invoked on condition of type SIMPLE-ERROR Don't know how to REQUIRE ASDF-JAR.
I guess I'm doing something wrong?
Thanks for your help,
Robert Dodier
_______________________________________________ Armedbear-devel mailing list Armedbear-devel@common-lisp.net http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel
I've loaded asdf-jar.lisp by hand and now I get a little farther.
(asdf-jar:package :maxima) #<THREAD "interpreter" {270664}>: Debugger invoked on condition of type FILE-ERROR Failed to read file for incoporation in zip archive.
This is thrown at line 227 in zip.java. Is there a way to find out what file it was trying to read?
best,
Robert Dodier
_______________________________________________ Armedbear-devel mailing list Armedbear-devel@common-lisp.net http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel
On 05 Dec 2014, at 20:08, Robert Dodier robert.dodier@gmail.com wrote:
I've loaded asdf-jar.lisp by hand and now I get a little farther.
(asdf-jar:package :maxima) #<THREAD "interpreter" {270664}>: Debugger invoked on condition of type FILE-ERROR Failed to read file for incoporation in zip archive.
This is thrown at line 227 in zip.java. Is there a way to find out what file it was trying to read?
If you are running under SLIME, you should drop out to the debugger, and be able to inspect the error to find the location.
See [abcl-servlet][1] for a recipe to start the SWANK server in non “from the REPL” environments like under the Java Servlet framework.
[1]: https://bitbucket.org/easye/abcl-servlet/src/b0e7e5353d6c92a1990ed1bb5500be1...
On 2014-12-06, Mark Evenson evenson@panix.com wrote:
If you are running under SLIME, you should drop out to the debugger, and be able to inspect the error to find the location.
Well, I'm not working with SLIME, and my attempt to use jdb didn't work as hoped ... wasn't able to set a breakpoint in an overloaded method (I don't remember the error but the jdb repl rejected what looked to me like a correct breakpoint).
For the moment I've stopped pursuing ASDF-JAR and decided to just load fasls from the file system (via ASDF) and that is working just as one would hope with Jetty as the servlet container. I will post some notes in case anyone else is interested.
best,
Robert Dodier
_______________________________________________ Armedbear-devel mailing list Armedbear-devel@common-lisp.net http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel
On 07 Dec 2014, at 06:49, Robert Dodier robert.dodier@gmail.com wrote:
On 2014-12-06, Mark Evenson evenson@panix.com wrote:
If you are running under SLIME, you should drop out to the debugger, and be able to inspect the error to find the location.
Well, I'm not working with SLIME, and my attempt to use jdb didn't work as hoped ... wasn't able to set a breakpoint in an overloaded method (I don't remember the error but the jdb repl rejected what looked to me like a correct breakpoint).
I’ve had good experience using Netbeans to connect to JVM processes for debugging, inclusive of setting breakpoints, but if I were to approach your problem I would first try to get the abcl.jar running in the Java Servlet context to start a SLIME swank server that I could then connect to to set the appropriate debug hooks.
For the moment I've stopped pursuing ASDF-JAR and decided to just load fasls from the file system (via ASDF) and that is working just as one would hope with Jetty as the servlet container. I will post some notes in case anyone else is interested.
I’m glad you got something to work!
armedbear-devel@common-lisp.net
-
Mark Evenson -
Robert Dodier