On Feb 10, 2009, at 8:52 PM, Stuart Sierra wrote: > Ok, new behavior in SVN rev. 449: Full stack traces are printed by > default. Bind *stack-trace-depth* to an integer to limit the depth.
That's great, Stuart, thank you very much. >> 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. Absolutely true -- there's often lots of noise in stack traces, but there's gems in there if you're willing to scan through them (and once you get the hang of it, your eyeballs learn how to ignore the noise). Just FWIW, we only use test-is in an automated test context that is bootstrapped by ant and hudson, so the full stack traces really need to be in the logs anyway in order for the testing to be maximally useful. - Chas --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
