-
Notifications
You must be signed in to change notification settings - Fork 152
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
"Unreachable code" messages when using gtest #177
Comments
Seconding. Not just with googletest, but also Catch2 presents the same issue. |
@mjeronimo I'm missing some details to reproduce exactly this message. There's no It seems like you are probably using this but just for info, I'll include a couple of details on related parameters that can be used. The first one is $ ikos --entry-points <alternative_main_function> hello_test.cc Gtest in particular provides a However, that option to $ ikos --entry-points '*' hello_test.cc Using As per Catch2, I get similar errors to the ones reported in this issue with:
|
Using IKOS in Google tests projects results in IKOS detecting unreachable code in global C++ objects. Apparently, IKOS is examining these global functions/constructors but sees no path to them from main (since they aren't called from main, but are invoked by the application startup-code before main is called). This was detected on Ubuntu 20.04.
To reproduce:
ikos-gtest-issue-1.zip
The text was updated successfully, but these errors were encountered: