wine/test.h: Identify test result lines printed by child processes.

Alexandre Julliard julliard at winehq.org
Mon Jan 30 14:41:56 CST 2017


Francois Gouget <fgouget at codeweavers.com> writes:

> Currently the child process result lines are indistinguishable from the
> main process one. This makes it impossible to automatically detect
> when a process exits abruptly, i.e. without printing a result line,
> if it has run a subprocess. By making the subprocess result lines
> different analysis tools will detect that the main result line is
> missing and automatically consider that the main process crashed,
> thus marking the test as failed.
>
> Signed-off-by: Francois Gouget <fgouget at codeweavers.com>
> ---
>
> This should fix bug 32354:
> https://bugs.winehq.org/show_bug.cgi?id=32354

I don't think the test framework should be modifying the environment in
all the tests. It already breaks some things:

../../../tools/runtest -q -P wine -T ../../.. -M msvcrt.dll -p msvcrt_test.exe.so environ && touch environ.ok
environ.c:198: Test failed: Expected environment block pointer element to be non-NULL
wine: Unhandled page fault on read access to 0x00000000 at address 0x7ed2a986 (thread 0074), starting debugger...


-- 
Alexandre Julliard
julliard at winehq.org



More information about the wine-devel mailing list