You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ scli run .
Exception in thread "main"
Exception: java.lang.StringIndexOutOfBoundsException thrown from the UncaughtExceptionHandler in thread "main"
$ scli run . --native
libc++abi: terminating due to uncaught exception of type scalanative::ExceptionWrapper: std::exception
fish: Job 1, 'scala-cli $argv' terminated by signal SIGABRT (Abort)
Note how there's at least some clue in JVM version as to what the original exception was
The text was updated successfully, but these errors were encountered:
For the 0.5.x series we should be able to use default Thread.uncoughtExceptionHandler, which later can be also customized. I'll try to adjust the generated main to allow for that
Seems like if you have an exception thrown while rendering another exception, you get a pretty scary C++ ABI error.
Consider this:
See the difference between JVM and Native:
Note how there's at least some clue in JVM version as to what the original exception was
The text was updated successfully, but these errors were encountered: