[prev in list] [next in list] [prev in thread] [next in thread] 

List:       hurd-bug
Subject:    Re: [Bug hurd/24110] SS_DISABLE never set in stack_t value returned by sigaltstack
From:       Samuel Thibault <samuel.thibault () gnu ! org>
Date:       2019-03-04 7:10:49
Message-ID: 20190304071049.36pwvfbmztk2ccjw () function
[Download RAW message or body]

Svante Signell, le dim. 03 mars 2019 23:21:55 +0100, a ecrit:
> On Fri, 2019-03-01 at 07:04 -0800, Samuel Thibault wrote:
> > Svante Signell, le lun. 25 févr. 2019 10:25:01 +0100, a ecrit:
> > > Unfortunately, the situation has not improved with it :(
> > > 
> > > The SIGILL failures are now SIGABRT and SIGSEGV as they became with the
> > > SS_DISABLE patch.
> > 
> > It however seems that the failures are different?
> > (possibly with much more understandable backtraces)
> 
> No they are not from a global tests perspective.

Well, some golang packages now do build fine.

> That requires further investigations.

That's what I meant by mentioning the backtraces.

Samuel

[prev in list] [next in list] [prev in thread] [next in thread]