-
Notifications
You must be signed in to change notification settings - Fork 534
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
cxx_restart test segfaults with flex 2.6.2 #98
Comments
I'm not seeing that, so... What's your platform and compiler? (And clearly that info should be a part of the log that gets generated or something like that.) |
Exherbo Linux (x86_64-pc-linux-gnu), gcc-6.2.0 After writing the above I just tried with gcc-5.4.0 and the test passes when compiled with that gcc version. |
with gcc6, does it matter which c++ variant you use? It defaults to c++14, iirc. |
I'm seeing this with GCC 6.2.0 on AMD64 as well. The line it crashes on (from flex.skl:2059) makes it pretty clear what the problem is:
(where Where's the code expecting the invalid reference to come from? The test calls |
Indeed, the C++ variant has no influence. |
Can we provide a dummy stream that is used when |
Hi,
More logs can be found here: |
My apologies for the commit spam, I hadn't realised that they'd show up here even before I had created the pull request. Anyway, creating a new dummy stream seems difficult due to lifetime management, but using the existing |
@hvdijk no worries at all. I'm looking forward to reviewing your pr, so thanks for that. |
flex 2.6.3
Therefore it seems that this issue is not resolved. Error in
from gdb:
from valgrind:
|
@davidnich The title just means this was reported against flex 2.6.2, it doesn't mean it got fixed in 2.6.3. It can't: 2.6.3 was already released on 30 Dec 2016, this bug was fixed 12 Jan 2017. It should make it into the next release. |
@hvdijk ok thank you for that information, good to hear! |
Sounds like it's high time for a new release then. |
Backtrace and log file (github didn't let me attach it) follow below:
The text was updated successfully, but these errors were encountered: