From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: [musl] [Bug] Do not ignore membarrier return code
Date: Tue, 24 Mar 2020 13:42:31 -0400 [thread overview]
Message-ID: <20200324174231.GY11469@brightrain.aerifal.cx> (raw)
In-Reply-To: <3addac2b-235b-1923-c43e-d31f29f2019e@adelielinux.org>
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 parent reply other threads:[~2020-03-24 17:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 16:10 Julio Guerra
2020-03-23 16:38 ` Rich Felker
2020-03-24 13:20 ` Julio Guerra
2020-03-24 13:53 ` Rich Felker
2020-03-24 13:53 ` Julio Guerra
2020-03-24 14:01 ` Rich Felker
2020-03-24 16:08 ` A. Wilcox
2020-03-24 17:42 ` Rich Felker [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200324174231.GY11469@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).