I agree that I'd like to (have an option to) see a whole stack trace, or barring that, bind the most recent exception to some var so I can look at it later (c.f. *e). The limited trace hindered my debugging just yesterday.
On Feb 10, 2:01 pm, Jeffrey Straszheim <straszheimjeff...@gmail.com> wrote: > I've found that, in general, the stack dumps you get back from Java (into > Clojure-land) are pretty unhelpful. I found that at first too, before someone showed me that you often have to look at the nested "cause" ((.getCause e), I think) of the exception, sometimes 5-10 layers deep, to see the real problem. It is almost always buried in there somewhere. -Jason --~--~---------~--~----~------------~-------~--~----~ 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 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 -~----------~----~----~----~------~----~------~--~---
