This isn't a CCW exclusive issue, but the Oracle JVM 'optimizing away' stacktraces.
It can be remedied by adding the '-XX:-OmitStackTraceInFastThrow' flag to the JVM startup parameters of the process you're starting. If Leiningen is used to start the JVM, add the following setting to your lein project.clj map: :jvm-opts ^:replace ["-XX:-OmitStackTraceInFastThrow"] Oh, and you're welcome.. On Wednesday, December 3, 2014 6:29:23 PM UTC+1, Fluid Dynamics wrote: > > It's a giant pain to debug exceptions without stack traces. This seems to > be a problem specific to CCW, as I don't encounter it using other > development environments. > > Is this going to be fixed anytime soon? > -- 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 --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
