On Mon, Feb 11, 2019 at 1:38 PM Svante Signell <svante.sign...@gmail.com> wrote: > > On Mon, 2019-02-11 at 10:27 -0800, Ian Lance Taylor wrote: > > > It sound like the right fix is to use #ifdef WIFCONTINUED in > > syscall/wait.c. If WIFCONTINUED is not defined, the Continued > > function should always return 0.
> I can also easily submit a patch for WIFCONTINUED returning 0. Problem is I'll > be AFK for the next week. Maybe this can wait, or you find a solution? > Regardinga comm opttion for ps Samuel is the best source. I've committed this patch that should fix this problem. Bootstrapped and tested on x86_64-pc-linux-gnu. Ian
Index: gcc/go/gofrontend/MERGE =================================================================== --- gcc/go/gofrontend/MERGE (revision 268785) +++ gcc/go/gofrontend/MERGE (working copy) @@ -1,4 +1,4 @@ -fc8aa5a46433d6ecba9fd1cd0bee4290c314ca06 +6d03c4c8ca320042bd550d44c0f25575c5311ac2 The first line of this file holds the git revision number of the last merge done from the gofrontend repository. Index: libgo/go/syscall/wait.c =================================================================== --- libgo/go/syscall/wait.c (revision 268369) +++ libgo/go/syscall/wait.c (working copy) @@ -16,6 +16,10 @@ #define WCOREDUMP(status) (((status) & 0200) != 0) #endif +#ifndef WIFCONTINUED +#define WIFCONTINUED(x) 0 +#endif + extern _Bool Exited (uint32_t *w) __asm__ (GOSYM_PREFIX "syscall.WaitStatus.Exited");
