Re: pkg/51170: SIGSEGV during build of nodejs4 with netbsd/current

[christos%zoulas.com@localhost (Christos Zoulas)]

The following reply was made to PR pkg/51170; it has been noted by GNATS.

From: christos%zoulas.com@localhost (Christos Zoulas)
To: Benjamin Lorenz <inbox@benjaminlorenz.email>, gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: pkg/51170: SIGSEGV during build of nodejs4 with netbsd/current
Date: Thu, 26 May 2016 10:41:58 -0400

 On May 26,  3:35pm, inbox@benjaminlorenz.email (Benjamin Lorenz) wrote:
 -- Subject: Re: pkg/51170: SIGSEGV during build of nodejs4 with netbsd/curren
 
 | Hi Christos,
 | 
 | about to recompile nodejs and checking if this helps.
 | 
 | I had another program, /usr/pkg/bin/mongo (from pkgsrc/databases/MongoDB), =
 | which crashed as well with a memory error. paxctl +m makes it run fine. Tha=
 | nks for your quick advise!
 | 
 | Does this mean the programs are buggy?
 
 They are misbehaving. They might need to do this or they might just
 be careless when mapping memory. PaX MPROTECT prevents programs
 from mapping memory that is both writable and executable at the
 same time. It will take away one or the other bit. Some programs
 (like just-in-time compilers for example java) need to do this
 because they generate code on the fly and they need to be able to
 write the code and execute it. Mongo apparently uses V8 internally:
 https://jira.mongodb.org/browse/SERVER-1592
 
 christos