Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
A memory read overrun issue in s_to_n32_unsafe.cc #215
This is the runtime error msg caused by the overrun.
Looks like it's caused by the test itself:
I'll try to add travis presubmit for a few sanitizers.
Eh, I didn't read the bug report properly.
Valgrind also reports the error:
referenced this issue
Sep 4, 2018
added a commit
Sep 4, 2018
It's a different bug. Can you open a new issue and specify what function overflowed? There is a number of recursive functions in re2c, and if the default stack size on your plaftorm is small (compared to that on the platforms where we test re2c), than it is quite possible that one of the recursive functions exhausted the stack.
No, actually it's to overflow re2c lexer buffer with an unexpectedly long lexeme: re2c used to crash at some point, but now it prints an error message.
What platform are you running re2c on? (My guess is, windows: I don't have it and the only kind of testing for windows is done by running Mingw-compiled re2c in Wine.)