[Bug 47125] Preloader fails to reserve a memory range when running under valgrind

https://bugs.winehq.org/show_bug.cgi?id=47125

--- Comment #2 from [e-mail] ---
(In reply to Austin English from comment #1)
> Does it actually cause a problem? I'm fairly certain that's expected
> behavior.

Expected behavior for what reason?  I don't know if this is a problem (valgrind
fails to recognize an instruction later and kills the program, then there's an
invalid write reported from the SIGILL handler), but if it were expected and
correct behavior, then why print a warning?