Periodic jextract failure on Windows

[Maurizio Cimadamore]

AFAIK, this is a known issue on Windows, and one that is proving to be 
elusive to narrow down.

We have seen this from time to time in our continuous builds.

It does not seem caused by the linker support, but, rather, from a bad 
interaction between libclang and the JVM. Jorn might have more details, 
as I think he did some investigation on this in the past.

Maurizio

On 29/04/2022 12:45, Duncan Gittins wrote:
> Some feedback on jextract - I'm using Windows OpenJDK 64-Bit Server VM
> (build 18+36-2087) and a recent build of jextract from Apr 15 (commit
> c1b0e7ec4c4c635f26ef19dbc5f3f3acc2b9f7ee) just after the Windows gradle
> build was fixed.
>
> Occasionally jextract fails on Windows, and gives simple message: "Child
> process exited with code xxxxxx". A re-run of same command works. I've seen
> this issue a few times in the last year on earlier JDK+jextract so the
> issue isn't specific to the above JDK+jextract combination.
>
> It does not make a difference which of my input configurations I use, but
> see contents of the @argfiles used below which caused the recent error
> message:
>
>      > %JEXTRACT% @headers\C.conf @headers\C.sym
>      WARNING: Using incubator modules: jdk.incubator.foreign
>      Child process exited with code 3221225477
>
>      >%JEXTRACT% @headers\C.conf @headers\C.sym
>      WARNING: Using incubator modules: jdk.incubator.foreign
>
> I've no reason to suspect my PC disk is beginning to fail which might be an
> explanation. Any suggestions?
>
> Kind regards
>
> Duncan Gittins
>
> C_h.h:
>
> #include <stdio.h>
> #include <process.h>
> #include <string.h>
> #include <stdlib.h>
> typedef _CoreCrtNonSecureSearchSortCompareFunction QsortCompareFunc;
>
> C_h.sym:
>
> --include-function strlen
> --include-function vprintf
> --include-function printf
> --include-function _getpid
> --include-function qsort
> --include-typedef QsortCompareFunc