[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Bug hurd/24110] SS_DISABLE never set in stack_t value returned by s
|
From: |
Samuel Thibault |
|
Subject: |
Re: [Bug hurd/24110] SS_DISABLE never set in stack_t value returned by sigaltstack |
|
Date: |
Mon, 4 Mar 2019 08:10:49 +0100 |
|
User-agent: |
NeoMutt/20170113 (1.7.2) |
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