| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
This should make it easier to debug exceptions falling out of the C++ code, as the C++ runtime will print the error message (the `what()` of the exception) on its way to aborting the program. Did a regex replace; removed the `char*` handler in CALL_CPP_FULL; and remove a bunch of extra whitespace.
|
Would prefer @mdboom or @ianthomas23 sign off on this before merging. |
Sorry, something went wrong.
There was a problem hiding this comment.
I'm happy with this.
Don't understand the AppVeyor failure.
Sorry, something went wrong.
Sorry, something went wrong.
|
Hm. CALL_CPP_FULL is used to catch C++ exceptions and convert them to Python. std::runtime_error is not handled by it (you just simply removed char const *e), so all these exception now will be caught by catch (...) and raise in Python with "Unknown exception in %s" message. |
Sorry, something went wrong.
|
Oops. New PR coming. |
Sorry, something went wrong.
Backport PR #9289 on branch v2.1.x
| Back | FazBrowse Home | New Git URL |
This should make it easier to debug exceptions falling out of the C++
code, as the C++ runtime will print the error message (the what() of
the exception) on its way to aborting the program.
Did a regex replace; removed the char* handler in CALL_CPP_FULL; and
remove a bunch of extra whitespace.
For example, before application of the patch in #9074, the failing code now gives
Should also help with #9244.
PR Summary
PR Checklist