-
-
Notifications
You must be signed in to change notification settings - Fork 1.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
Fuzzer fails immediately due to abseil: AddressSanitizer: SEGV #1335
Comments
It's basically failing here, in absl::flat_hash_map<std::string, LogLevel> Settings::String2LogLevel =
{
{ "debug", LogLevel::LOG_DEBUG },
{ "warn", LogLevel::LOG_WARN },
{ "error", LogLevel::LOG_ERROR },
{ "none", LogLevel::LOG_NONE }
}; which BTW is perfectly valid according to docs: https://abseil.io/docs/cpp/guides/container#construction |
The error does not happen if this line is removed from meson.build. Here few places with some info. |
I'm going to try with a newest clang version. EDIT: same error with clang version: Ubuntu clang version 16.0.6 (15), in the latest stable ubuntu (23.10) |
I don't know, but remove it and the error will raise somewhere else. |
Apparently those flags (-fsanitize,fuzzer) need to be propagated everywhere including the abseil dependency. |
I'm working on the fix. I'll open a separate PR. |
I'm pretty sure that if we remove
And how can we do that? Can we set some env or variable in meson.build that also makes other subprojects receive those C flags? |
Of course :-), but it gave me the clue of what was happening. |
This issue blocks PR #1338 for obvious reasons :) |
Yes, I'll do a PR to wrapdb today |
Note: fixing this in PR #1338 as a bonus. |
Your environment
Issue description
The text was updated successfully, but these errors were encountered: