IndexOutOfBoundsException for exceptions with no stack trace filled in #25
weissjeffm
commented
Jul 17, 2013
The :jvm-opts did work around the problem so that option being on by default does seem to be the root cause.
nahuel
commented
Aug 19, 2013
I just opened a bug and an analysis before seeing this one, is related: #26
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Now, how I end up with an exception with no stack trace in production, I am not 100% sure. I suspect it is the jvm optimization that leaves out stacktraces in recurring exceptions:
http://stackoverflow.com/questions/4659151/recurring-exception-without-a-stack-trace-how-to-reset
I should be able to work around the problem with
:jvm-opts ["-XX:-OmitStackTraceInFastThrow"]but haven't tried it yet.
clj-stacktrace shouldn't be assuming there is a non-zero length array of StackTraceElement.
Fix should be pretty straightforward, will try to submit a pr.