Looks like you figured this out, but sharing in case it helps others. It turns out the JVM actually has a special caching mechanism for making NullPointerExceptions fast (and near-impossible to debug):
http://stackoverflow.com/a/3010106 This link also has a JVM opt to stop this optimization, and mentions that you always get the full stack trace *once* before it's optimized away. On Monday, September 1, 2014 7:11:00 AM UTC-7, g vim wrote: > > Compiling a file in Emacs, this error: > > "NullPointerException clojure.lang.Numbers.ops (Numbers.java:961)" > > ..... leaves me clueless as to where the error occurred. > > Is there hope for native Clojure debugging anytime soon as this is the > kind of thing which can easily drive a non-Java user like me to > distraction? I noticed the Elixir community had the same problem with > Erlang's cryptic error messages and produced their own error logging to > make the language attractive to non-Erlangers. This seems to me to be > perhaps the biggest barrier to entry with hosted languages. We can't > expect everyone coming to Clojure to master Java's less-than-helpful > error messages. Many will just give up. > > gvim > > > > -- 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.
