Fuzzer fails immediately due to abseil: AddressSanitizer: SEGV about mediasoup

[jmillan]

PR mesonbuild/wrapdb#1412

[ibc]

It's basically failing here, in Settings.cpp:

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

[jmillan]

The error does not happen if this line is removed from meson.build.

Here few places with some info.

• google/re2#451
• abseil/abseil-cpp#1524 (comment)

[jmillan]

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)

[jmillan]

Why are we using abseil to just hold a map or string->integer?

I don't know, but remove it and the error will raise somewhere else.

[jmillan]

Apparently those flags (-fsanitize,fuzzer) need to be propagated everywhere including the abseil dependency.

[jmillan]

I'm working on the fix. I'll open a separate PR.

[ibc]

I'm pretty sure that if we remove '-fsanitize=address,fuzzer' then we are not fuzzing anything XD

Apparently those flags (-fsanitize,fuzzer) need to be propagated everywhere including the abseil dependency.

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?

[jmillan]

'-fsanitize=address,fuzzer' then we are not fuzzing anything XD

Of course :-), but it gave me the clue of what was happening.

[ibc]

This issue blocks PR #1338 for obvious reasons :)

[jmillan]

Yes, I'll do a PR to wrapdb today

[ibc]

Note: fixing this in PR #1338 as a bonus.