Re: [PATCH v9 0/6] MR6004: comctl32: A NULL string fix.

[Aida Jonikienė (＠DodoGTA)]

On Wed Jul 31 08:42:15 2024 +0000, Nikolay Sivov wrote:
> I don't think I follow how tests results were translated to code
> changes. If it crashes on NULL buffer on Windows, which it does, why are
> we not doing the same? Having 0 length and NULL buffer is fine, having
> non-zero length and NULL buffer crashes, so why are we checking output pointer?

This MR was intended to be a quick fix for the Zadig program but it snowballed into these 6 patches because of test requirements and other unrelated code changes

I might try to make the test behavior closer to Windows but isn't better memory safety a good thing?