-
-
Notifications
You must be signed in to change notification settings - Fork 493
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
C++ Exception Handling broke in 3.3.0 #1508
Comments
I get "Exception: Foobar" in both debug and release builds of branch develop. |
Sorry it took a while to respond, but when I tested this again, I saw even weirder behavior. In fact there was no output anymore! It just ignored that an exception was thrown. I should have noted that I use LuaJIT. Maybe that has something to do with it? But even with LuaJIT this worked fine in v3.2.1. I made some tests in this repo: https://github.com/pfirsich/sol2_issue_1508 |
I did read it, but frankly I did not understand it completely. I tried defining I actually saw the comment in #1386 you linked before, but I wasn't sure if it's the same and didn't want to use inofficial versions of sol2 for now. I guess this might be worth a try for someone that actually wants to debug this. I mostly want to report this regression. I only use exceptions to terminate the program essentially, so I have replaced it with an exit, so I don't need a fix soon. |
With 3.2.2 this produces the following output:
With 3.3.0 the output is this instead:
This looks like a bug to me. Also is there a workaround to get the
exception.what()
string in 3.3.0?Also for some reason the SOL_VERSION_STRING is "3.5.0" for 3.2.2 and "3.2.3" for 3.3.0. That is very confusing to say the least. I honestly think this might be worth re-releasing them just for that version string fix alone.
The text was updated successfully, but these errors were encountered: