Re: [Bug hurd/24110] SS_DISABLE never set in stack_t value returned by sigaltstack

2019-01-23 Thread Joshua Branson
Samuel Thibault writes: > Hello, > > Could somebody give this a try? > > Samuel > > samuel.thiba...@ens-lyon.org, le dim. 20 janv. 2019 16:48:19 +, a ecrit: >> https://sourceware.org/bugzilla/show_bug.cgi?id=24110 >> >> --- Comment #3 from Samuel Thibault --- >> Created attachment 11553 >>

Re: [Bug hurd/24110] SS_DISABLE never set in stack_t value returned by sigaltstack

2019-01-23 Thread Svante Signell
Hi, I'll take a look. Maybe these issues are causing the SIGILL errors in the gcc libgo tests. BBL. On Wed, 2019-01-23 at 00:28 +0100, Samuel Thibault wrote: > Hello, > > Could somebody give this a try? > > Samuel > > samuel.thiba...@ens-lyon.org, le dim. 20 janv. 2019 16:48:19 +, a ecrit:

Re: [Bug hurd/24110] SS_DISABLE never set in stack_t value returned by sigaltstack

2019-01-23 Thread Samuel Thibault
Svante Signell, le mer. 23 janv. 2019 15:37:06 +0100, a ecrit: > I'll take a look. Maybe these issues are causing the SIGILL errors in the gcc > libgo tests. They might be indeed. Samuel