Re: seg fault building npm

[Chavdar Ivanov <ci4ic4%gmail.com@localhost>]

Any more ideas about this nodejs fault? Latest firefox builds now
require nodejs to be installed.

node panics in ecp_nistz256_points_mul, part of the built-in
dependence openssl. The used one is 1.1.0, whereas ours is 1.1.1, I
would presume patched appropriately and tested as part of the main
system (this is under -current as of a couple of days ago).

---
# gdb =node
                                              18-11-09 - 1[9/1843]
GNU gdb (GDB) 8.0.1
...
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/pkg/bin/node...(no debugging symbols found)...done.
(gdb) run bin/npm-cli.js install
Starting program: /usr/pkg/bin/node bin/npm-cli.js install
[New LWP 1 of process 21164]
[New LWP 10 of process 21164]stall: sill install executeActions
[New LWP 11 of process 21164]stall: sill install executeActions
[New LWP 9 of process 21164]
[New LWP 8 of process 21164]
[New LWP 7 of process 21164]
[New LWP 6 of process 21164]
[New LWP 5 of process 21164]
[New LWP 4 of process 21164]
[New LWP 3 of process 21164]
[New LWP 2 of process 21164]

Thread 2 received signal SIGSEGV, Segmentation fault.
0x000000000094cf11 in ecp_nistz256_points_mul ()
(gdb) bt
#0  0x000000000094cf11 in ecp_nistz256_points_mul ()
#1  0x0000000000000000 in ?? ()
(gdb) info threads
  Id   Target Id         Frame
  1    process 21164     0x0000785c48aa9cea in ___lwp_park60 () from
/usr/lib/libc.so.12
* 2    LWP 1 of process 21164 0x000000000094cf11 in ecp_nistz256_points_mul ()
  3    LWP 10 of process 21164 0x0000785c48aa9cea in ___lwp_park60 ()
from /usr/lib/libc.so.12
...


[New LWP 2 of process 21164]

Thread 2 received signal SIGSEGV, Segmentation fault.
0x000000000094cf11 in ecp_nistz256_points_mul ()
(gdb) bt
#0  0x000000000094cf11 in ecp_nistz256_points_mul ()
#1  0x0000000000000000 in ?? ()
(gdb) info threads
  Id   Target Id         Frame
  1    process 21164     0x0000785c48aa9cea in ___lwp_park60 () from
/usr/lib/libc.so.12
* 2    LWP 1 of process 21164 0x000000000094cf11 in ecp_nistz256_points_mul ()
  3    LWP 10 of process 21164 0x0000785c48aa9cea in ___lwp_park60 ()
from /usr/lib/libc.so.12
  4    LWP 11 of process 21164 0x0000785c48aa9cea in ___lwp_park60 ()
from /usr/lib/libc.so.12


Chavdar

On Thu, 18 Oct 2018 at 23:51, Mike Pumford <mpumford%mudcovered.org.uk@localhost> wrote:
>
>
>
> On 18/10/2018 23:42, Mike Pumford wrote:
> >
> >
> > On 18/10/2018 23:16, Mike Pumford wrote:
> >
> >> in the build directory in between the make and the make install. I'm
> >> not familiar enough with the pkgsrc make targets (and paxctl) to know
> >> the best way to make that happen. My guess is to do it in the
> >> preinstall target. Am I right?
> >>
> >> I'm also looking at the gfind dependency as well as that looks like a
> >> relatively simple makefile patch.
> >>
> >> Not sure if this will help with the npm issue but one problem at a
> >> time. :)
> >>
> > Okay manually doing the following before make install gets rid of the
> > odd errors building node:
> >
> > 1. paxctl +m out/Release/node
> > 2. substitute ! for -not in the Makefile
> The second one of these is something we should be able to persuade
> nodejs to change upstream although I doubt the patch is hard. as ! is
> posix compliant but -not is a GNU extension at least according to the
> find man page on my ubuntu VM. I'll see if I can figure out a patch for
> the makefile and the paxctl as a first step and keep investigating the
> npm issue. I guess I'll be trying to persuade pkgsrc to build a debug
> version of the node binary.
>
> Mike



-- 
----