pkgsrc-Bugs archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

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

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

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

 --=-+6FPdhDN9cixzT0IJ1jw
 Content-Type: text/plain; charset="utf-8"
 Content-Transfer-Encoding: quoted-printable
 
 Hi Christos,
 
 
 They are misbehaving. They might need to do this or they might just=20
 be careless when mapping memory. PaX MPROTECT prevents programs=20
 from mapping memory that is both writable and executable at the=20
 same time. It will take away one or the other bit. Some programs=20
 (like just-in-time compilers for example java) need to do this=20
 because they generate code on the fly and they need to be able to=20
 write the code and execute it. Mongo apparently uses V8 internally:=20
 https://jira.mongodb.org/browse/SERVER-1592=C2=A0
 
 
 
 
 
 Yes, indeed, the two problematic programs share some code.
 
 
 How to fix this problem? Is it about changing the pkgsrc build process, to =
 include the paxctl call?=C2=A0
 
 
 And, why did this problem not occur back in January? Did we change our memo=
 ry management to become more pedantic in the last months?
 
 
 Cheers,
 Benjamin
 
 =
 
 --=-+6FPdhDN9cixzT0IJ1jw
 Content-Type: text/html; charset="utf-8"
 
 <html><head></head><body>Hi Christos,<div><br><div><blockquote class="mori" style="margin:0 0 0 .8ex;border-left:1px solid #CCC;padding-left:1ex;">They are misbehaving. They might need to do this or they might just
 <br>be careless when mapping memory. PaX MPROTECT prevents programs
 <br>from mapping memory that is both writable and executable at the
 <br>same time. It will take away one or the other bit. Some programs
 <br>(like just-in-time compilers for example java) need to do this
 <br>because they generate code on the fly and they need to be able to
 <br>write the code and execute it. Mongo apparently uses V8 internally:
 <br>https://jira.mongodb.org/browse/SERVER-1592&nbsp;</blockquote></div></div><br><div><div><blockquote class="mori" style="margin:0 0 0 .8ex;border-left:1px solid #CCC;padding-left:1ex;"></blockquote></div></div><div><div><blockquote class="mori" style="margin:0 0 0 .8ex;border-left:1px solid #CCC;padding-left:1ex;"></blockquote></div></div><div>Yes, indeed, the two problematic programs share some code.</div><div><br></div><div>How to fix this problem? Is it about changing the pkgsrc build process, to include the paxctl call?&nbsp;</div><div><br></div><div>And, why did this problem not occur back in January? Did we change our memory management to become more pedantic in the last months?</div><div><br></div><div>Cheers,</div><div>Benjamin</div><div><br></div></body></html>
 --=-+6FPdhDN9cixzT0IJ1jw--
Home | Main Index | Thread Index | Old Index