Skip to content

C++ exceptions in libc++ currently unwind through main instead of crashing with a backtrace #5225

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

Open
danakj opened this issue Mar 31, 2025 · 2 comments

Comments

@danakj
Copy link
Contributor

danakj commented Mar 31, 2025

https://discord.com/channels/655572317891461132/655578254970716160/1350190049479884822

There is some mysterious flag we need to pass to clang, since our libc++ is compiled with exceptions enabled to make them abort when they reach the edge of exception-enabled code.

@danakj
Copy link
Contributor Author

danakj commented Mar 31, 2025

I don't actually see us passing -fno-exceptions or -fno-cxx-exceptions in our bazel rules, so not sure if the diagnosis above from discord is correct.

@danakj
Copy link
Contributor Author

danakj commented Mar 31, 2025

I also don't see any obvious flags in https://clang.llvm.org/docs/ClangCommandLineReference.html related to this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant