Hi, Am 26.09.2009 um 17:06 schrieb Constantine Vetoshev:
This seems indeed useless at a first glance, but looking down the cause trace usually shows the real problem.Full stack trace follows, although I still don't know what it means. No message. [Thrown class java.lang.ExceptionInInitializerError] Backtrace: 0: sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) 1: sun.reflect.NativeConstructorAccessorImpl.newInstance (NativeConstructorAccessorImpl.java:39) 2: sun.reflect.DelegatingConstructorAccessorImpl.newInstance (DelegatingConstructorAccessorImpl.java:27) 3: java.lang.reflect.Constructor.newInstance(Constructor.java:513) 4: java.lang.Class.newInstance0(Class.java:355) 5: java.lang.Class.newInstance(Class.java:308) 6: clojure.lang.Compiler$FnExpr.eval(Compiler.java:3428) 7: clojure.lang.Compiler.eval(Compiler.java:4531) 8: clojure.core$eval__3990.invoke(core.clj:1728)
No. This is a *stack*trace. I meant the *cause* trace. That is, the chain of wrapped exceptions. You should look in the trace for lines like "Caused by ...". The last should point to the real problem. Of course, that might be something obscure, eg. in the case Chouser mentioned. However I found it to be something in my code in 99.9% of the cases. :] From what you print, it seems you use SLIME. This maybe hides the "Caused by..." lines and only prints the stracktrace. Not sure, though.
Sincerely Meikel
smime.p7s
Description: S/MIME cryptographic signature
