3 ms·
How is Clojure debugging now? Last I checked, I couldn't get a reliable stack trace, and the advice I read online said "just step through it" or use somesuch to
by m0th87 16y ago
How is Clojure debugging now? Last I checked, I couldn't get a reliable stack trace, and the advice I read online said "just step through it" or use somesuch tool, which is presumably not very helpful when you're trying to figure out why an hour-long application unexpectedly crashed. That was enough to scare me away.
- jshen 16y agoI'm not sure what you mean by "reliable stack trace", but I've been doing clojure full time for the past 6 months or so. Our program needs to stay up and it is heavily threaded. In this context I haven't had any problems with stack traces and my app fits your description of hours long run time and some crashes.
- runevault 16y agoThere are still thick stack traces by default, but there are tools to help now. http://clojure.org/libraries#Clojure%20Libraries-Category:%20xml-clojure.contrib.stacktrace http://clojure.org/libraries#Clojure%20Libraries-Category:%2...
- sbochins 16y agoNever knew there was an issue with stack traces in Clojure. I only started programming in it several months ago. From what I've found, its much easier to wade through stack traces in Clojure. You can break out at different points in the stack and have a running repl with that environment. I've found this to be very helpful with debugging.