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

List:       musl
Subject:    Re: [musl] [Bug] Do not ignore membarrier return code
From:       Rich Felker <dalias () libc ! org>
Date:       2020-03-24 17:42:31
Message-ID: 20200324174231.GY11469 () brightrain ! aerifal ! cx
[Download RAW message or body]

On Tue, Mar 24, 2020 at 11:08:10AM -0500, A. Wilcox wrote:
> On 24/03/2020 09:01, Rich Felker wrote:
> > On Tue, Mar 24, 2020 at 02:53:21PM +0100, Julio Guerra wrote:
> >>> But I wanted to give you more details with stack traces of the
> >>> segfault by retrying today with gdb but I cannot reproduce it
> >>> anymore...!
> >>> I'll retry later to see if I see the error again...
> >>
> >> The node:10.19-alpine image has been updated since yesterday! That may
> >> be why I don't have the issue anymore? It updated the latest
> >> alpine:3.11 image, so 3.11.5.
> >> The changelog talks says "main/musl: backport fixes from 1.2.0":
> >> https://www.alpinelinux.org/posts/Alpine-3.11.5-released.html
> > 
> > I'm not aware of any changes that are at all related to your problem.
> > 
> > Rich
> 
> My first guess is something to do with the really egregious inspector
> signal stack bug.  Our patch for Node 10.x is at:
> 
> https://code.foxkit.us/adelie/packages/blob/master/user/node/stack-silliness.patch
> 
> Alpine doesn't patch it for Node 12 because Node 12 has this code to
> purportedly "handle musl":
> 
> https://github.com/nodejs/node/blob/master/src/inspector_agent.cc#L112
> 
> But I still feel like it may be wrong.

I think this may be the cause. I don't think Alpine ever had the patch
Adélie had to fix this bug in node, but 3.11.5 has Node 12.15.0 which
has the above fix. It looks like Alpine 3.11.0 has 12.14.0 which
should also have the fix though...

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