Stas Sergeev

In a mean time, could you please make CI to run with asan enabled? That would be really cool, as currently I have asan disabled, its too slow. But with...

Except that -d no longer enables asan, and that's the whole point. Enabling sanitizers, even for devel builds, proved to be hard, as it produces very slow and barely usable...

` AttributeError: 'NoneType' object has no attribute 'group'` is what the errors are saying. So not too much to fix on my side. Besides, asan was enabled for -d for...

I think there are 2 unrelated errors: ``` msdos_ldt.c:264:48: runtime error: applying non-zero offset 65536 to null pointer SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior msdos_ldt.c:264:48 in ``` This seems to be from ubsan....

So how to reproduce this off-line?

This one is the asan bug. I wonder about the clang-specific one. As maybe clang triggers something new.

Seems like I can reproduce it w/o any examples. :)

I fixed the ubsan support, but asan is now broken by this: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84428 So I suppose asan is permanently broken and should not be enabled... Which is quite a shame...

I worked around the asan problem so it can now be enabled for a test. But more importantly, I think we miss the ubsan errors, that is always enabled. You...

I think basically any stderr output should be alerted. What do you think?