-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Buffer Overflow #1225
Comments
There is more:
|
Potentially false positives, due to not having instrumented the standard library. Take with a grain of salt, and re-test with an instrumented libcxx. |
horenmar
pushed a commit
that referenced
this issue
May 29, 2018
Until now, the stack size for POSIX signal handling was determined by the implementation defined limit `STKSZ`, which in some cases turned out to be insufficient, leading to stack overflow inside the signal handler. The new size, which was determined experimentally, is the larger of 32kb or `MINSTKSZ`. Fixes #1225
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
It seems to me that there is a buffer overflow in the signal handling routine.
Are you doing shenanigans in there? The only C++ legal thing to do in a signal handler is setting a
volatile sigatomic_t
, anything else is UB.(POSIX has a different opinion on that, and is saying that pretty much all the syscalls are fine. C or C++ stdlib is still off-limits, though)
Steps to reproduce
TEST_CASE
Report
Extra information
The text was updated successfully, but these errors were encountered: