I have the same problem, but you can usually figure that out by looking at the function to which the backtrace refers, as well as the filename:
4: clojure.lang.RT.nth(RT.java:722) 5: ddsolve.core$play_deal_strategically.invoke(core.clj:177) 6: ddsolve.core$eval2129.invoke(NO_SOURCE_FILE:1) 7: clojure.lang.Compiler.eval(Compiler.java:5424) Here I can tell that the problem was in ddsolve.core, not some other core.clj, from looking at line 5. On Aug 25, 7:06 am, David Jagoe <davidja...@gmail.com> wrote: > Ahoy, > > On 25 August 2010 15:46, Stuart Halloway <stuart.hallo...@gmail.com> wrote: > > > > > *Specific* documentation of pain points also welcome. > > In general I haven't found the stack traces to be too much of a > problem, but the lack of full paths in the trace has bitten me. Since > all of my namespaces have a core.clj this can mean a bit of detective > work to find which core.clj is being reported. > > Cheers, > David -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
