Bug#878674: [Pkg-javascript-devel] Bug#878674: Bug#878674: nodejs segfaults when building d3-* with webpack

2018-01-04 Thread Mattia Rizzolo 
Control: fixed -1 8.9.3~dfsg-1

On Mon, Dec 18, 2017 at 09:55:37PM +0100, Jérémy Lal wrote:
> Good news: i don't get this segfault using nodejs 8.9.3 that i just
> uploaded to experimental.

Tweaking metadata to say so, then.

This bug should probably also be closed at some point.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#878674: nodejs segfaults when building d3-* with webpack

2017-12-29 Thread Pirate Praveen 
Control: severity -1 grave

On Mon, 13 Nov 2017 23:21:03 +0100 =?UTF-8?B?SsOpcsOpbXkgTGFs?=
 wrote:
> I'd like to lower the severity of this bug because it concerns code
that is
> not (yet) in debian. We'll raise it again if/when node-d3-zoom crashes
when
> building on build server.

segfault has reached the build server and raising the severity.

https://buildd.debian.org/status/fetch.php?pkg=node-es6-promise=all=4.1.1%2Bds-1=1514582110=0

I guess it makes sense to reupload nodejs 8.9 to unstable sooner.



signature.asc
Description: OpenPGP digital signature

Bug#878674: [Pkg-javascript-devel] Bug#878674: Bug#878674: nodejs segfaults when building d3-* with webpack

2017-12-18 Thread Jérémy Lal 
2017-11-14 10:35 GMT+01:00 Jérémy Lal :

>
>
> 2017-11-14 8:51 GMT+01:00 Pirate Praveen :
>
>> On ചൊവ്വ 14 നവംബര്‍ 2017 03:51 രാവിലെ, Jérémy Lal wrote:
>> > Using only debian packages (and no npm-installed module) I can't
>> > reproduce the segfault in debian/sid:
>> >
>> > dev:~/Software/debian/node-d3-zoom/node-d3-zoom master$ webpack
>> --config
>> > debian/webpack.config.js index.js build/d3-zoom.js --target=web
>> > --output-library=d3-zoom --output-library-target=umd --module-bind
>> > 'js=babel-loader'
>>
>> [...]
>>
>> > WARNING in ./src/zoom.js
>> > 235:4-11 "export 'default' (imported as 'noevent') was not found in
>> > './noevent'
>> >
>> > WARNING in ./src/zoom.js
>> > 260:6-13 "export 'default' (imported as 'noevent') was not found in
>> > './noevent'
>> >
>> > WARNING in ./src/zoom.js
>> > 272:6-13 "export 'default' (imported as 'noevent') was not found in
>> > './noevent'
>> >
>> > WARNING in ./src/zoom.js
>> > 285:4-11 "export 'default' (imported as 'noevent') was not found in
>> > './noevent'
>> >
>> > WARNING in ./src/zoom.js
>> > 335:4-11 "export 'default' (imported as 'noevent') was not found in
>> > './noevent'
>> >
>> > WARNING in ./src/zoom.js
>> > 377:74-82 "export 'default' (imported as 'constant') was not found in
>> > './constant'
>> >
>> > WARNING in ./src/zoom.js
>> > 381:70-78 "export 'default' (imported as 'constant') was not found in
>> > './constant'
>> >
>> > WARNING in ./src/zoom.js
>> > 385:73-81 "export 'default' (imported as 'constant') was not found in
>> > './constant'
>> >
>> > WARNING in ./src/zoom.js
>> > 389:70-78 "export 'default' (imported as 'constant') was not found in
>> > './constant'
>> > dev:~/Software/debian/node-d3-zoom/node-d3-zoom master$
>> >
>>
>> It seems you are not using the .babelrc, do an quilt push -a and rerun
>> the command.
>>
>
> Right ! Now i reproduce the segfault.
> I tried with nodejs 6.12.0, uv 1.15.0, zlib1g 1.2.11 without success.
> Now i'm trying with embedded copies of uv and zlib... if you see it not
> crashing with nodesource, i'll eventually find what's causing it.
>
>
Good news: i don't get this segfault using nodejs 8.9.3 that i just
uploaded to experimental.

Jérémy

Bug#878674: [Pkg-javascript-devel] Bug#878674: nodejs segfaults when building d3-* with webpack

2017-11-14 Thread Jérémy Lal 
2017-11-14 8:51 GMT+01:00 Pirate Praveen :

> On ചൊവ്വ 14 നവംബര്‍ 2017 03:51 രാവിലെ, Jérémy Lal wrote:
> > Using only debian packages (and no npm-installed module) I can't
> > reproduce the segfault in debian/sid:
> >
> > dev:~/Software/debian/node-d3-zoom/node-d3-zoom master$ webpack --config
> > debian/webpack.config.js index.js build/d3-zoom.js --target=web
> > --output-library=d3-zoom --output-library-target=umd --module-bind
> > 'js=babel-loader'
>
> [...]
>
> > WARNING in ./src/zoom.js
> > 235:4-11 "export 'default' (imported as 'noevent') was not found in
> > './noevent'
> >
> > WARNING in ./src/zoom.js
> > 260:6-13 "export 'default' (imported as 'noevent') was not found in
> > './noevent'
> >
> > WARNING in ./src/zoom.js
> > 272:6-13 "export 'default' (imported as 'noevent') was not found in
> > './noevent'
> >
> > WARNING in ./src/zoom.js
> > 285:4-11 "export 'default' (imported as 'noevent') was not found in
> > './noevent'
> >
> > WARNING in ./src/zoom.js
> > 335:4-11 "export 'default' (imported as 'noevent') was not found in
> > './noevent'
> >
> > WARNING in ./src/zoom.js
> > 377:74-82 "export 'default' (imported as 'constant') was not found in
> > './constant'
> >
> > WARNING in ./src/zoom.js
> > 381:70-78 "export 'default' (imported as 'constant') was not found in
> > './constant'
> >
> > WARNING in ./src/zoom.js
> > 385:73-81 "export 'default' (imported as 'constant') was not found in
> > './constant'
> >
> > WARNING in ./src/zoom.js
> > 389:70-78 "export 'default' (imported as 'constant') was not found in
> > './constant'
> > dev:~/Software/debian/node-d3-zoom/node-d3-zoom master$
> >
>
> It seems you are not using the .babelrc, do an quilt push -a and rerun
> the command.
>

Right ! Now i reproduce the segfault.
I tried with nodejs 6.12.0, uv 1.15.0, zlib1g 1.2.11 without success.
Now i'm trying with embedded copies of uv and zlib... if you see it not
crashing with nodesource, i'll eventually find what's causing it.

Jérémy



>
> > I'd like to lower the severity of this bug because it concerns code that
> is
> > not (yet) in debian. We'll raise it again if/when node-d3-zoom crashes
> when
> > building on build server.
>
> ok, makes sense.
>

The least i can say is that it's the first node segfault i see in a while !

Jérémy

Bug#878674: [Pkg-javascript-devel] Bug#878674: nodejs segfaults when building d3-* with webpack

2017-11-13 Thread Pirate Praveen 
On ചൊവ്വ 14 നവംബര്‍ 2017 03:51 രാവിലെ, Jérémy Lal wrote:
> Using only debian packages (and no npm-installed module) I can't
> reproduce the segfault in debian/sid:
> 
> dev:~/Software/debian/node-d3-zoom/node-d3-zoom master$ webpack --config
> debian/webpack.config.js index.js build/d3-zoom.js --target=web
> --output-library=d3-zoom --output-library-target=umd --module-bind
> 'js=babel-loader'

[...]

> WARNING in ./src/zoom.js
> 235:4-11 "export 'default' (imported as 'noevent') was not found in
> './noevent'
> 
> WARNING in ./src/zoom.js
> 260:6-13 "export 'default' (imported as 'noevent') was not found in
> './noevent'
> 
> WARNING in ./src/zoom.js
> 272:6-13 "export 'default' (imported as 'noevent') was not found in
> './noevent'
> 
> WARNING in ./src/zoom.js
> 285:4-11 "export 'default' (imported as 'noevent') was not found in
> './noevent'
> 
> WARNING in ./src/zoom.js
> 335:4-11 "export 'default' (imported as 'noevent') was not found in
> './noevent'
> 
> WARNING in ./src/zoom.js
> 377:74-82 "export 'default' (imported as 'constant') was not found in
> './constant'
> 
> WARNING in ./src/zoom.js
> 381:70-78 "export 'default' (imported as 'constant') was not found in
> './constant'
> 
> WARNING in ./src/zoom.js
> 385:73-81 "export 'default' (imported as 'constant') was not found in
> './constant'
> 
> WARNING in ./src/zoom.js
> 389:70-78 "export 'default' (imported as 'constant') was not found in
> './constant'
> dev:~/Software/debian/node-d3-zoom/node-d3-zoom master$ 
>  

It seems you are not using the .babelrc, do an quilt push -a and rerun
the command.

> I'd like to lower the severity of this bug because it concerns code that is
> not (yet) in debian. We'll raise it again if/when node-d3-zoom crashes when
> building on build server.

ok, makes sense.



signature.asc
Description: OpenPGP digital signature

Bug#878674: [Pkg-javascript-devel] Bug#878674: Bug#878674: Bug#878674: Bug#878674: Bug#878674: Bug#878674: Bug#878674: nodejs segfaults when building d3-* with webpack

2017-11-13 Thread Jérémy Lal 
Severity: important
thanks


2017-11-07 18:49 GMT+01:00 Jérémy Lal :

>
>
> 2017-10-25 16:04 GMT+02:00 Pirate Praveen :
>
>> On ബുധന്‍ 25 ഒക്ടോബര്‍ 2017 07:08 വൈകു, Pirate Praveen wrote:
>> > I can reach the segfaulting point faster by setting break point at
>> > thread creation
>> >
>> > b pthread_create.c:333
>> >
>> > after 8 c, I reach the segfault point.
>> >
>> >
>> >
>>
>> hopefully more useful bt
>>
>> (gdb) bt
>> #0  node::fs_req_wrap::~fs_req_wrap (this=,
>> __in_chrg=) at ../src/node_file.cc:334
>> #1  node::Open (args=...) at ../src/node_file.cc:1063
>> #2  0x3b905decccb8 in ?? ()
>> #3  0x7fff8fc7a418 in ?? ()
>> #4  0x7fff8fc7a468 in ?? ()
>> #5  0x0003 in ?? ()
>> #6  0x in ?? ()
>> (gdb) s
>> node::Open (args=...) at ../src/node_file.cc:1064
>> 1064in ../src/node_file.cc
>> (gdb) bt
>> #0  node::Open (args=...) at ../src/node_file.cc:1064
>> #1  0x3b905decccb8 in ?? ()
>> #2  0x7fff8fc7a418 in ?? ()
>> #3  0x7fff8fc7a468 in ?? ()
>> #4  0x0003 in ?? ()
>> #5  0x in ?? ()
>> (gdb) s
>> v8::ReturnValue::Set (i=, this=)
>> at ../src/node_file.cc:1064
>> 1064in ../src/node_file.cc
>> (gdb) s
>> v8::internal::Internals::IntToSmi (value=)
>> at ../src/node_file.cc:1064
>> 1064in ../src/node_file.cc
>> (gdb) s
>> v8::internal::SmiTagging<8ul>::IntToSmi (value=)
>> at ../src/node_file.cc:1064
>> 1064in ../src/node_file.cc
>> (gdb) s
>> v8::internal::IntToSmi<31> (value=)
>> at ../deps/v8/include/v8.h:7274
>> 7274../deps/v8/include/v8.h: No such file or directory.
>> (gdb) s
>> node::Open (args=...) at ../src/node_file.cc:1063
>> 1063../src/node_file.cc: No such file or directory.
>> (gdb) s
>> node::fs_req_wrap::~fs_req_wrap (this=0x7fff8fc79db0,
>> __in_chrg=) at ../src/node_file.cc:334
>> 334 in ../src/node_file.cc
>> (gdb) s
>> uv_fs_req_cleanup (req=req@entry=0x7fff8fc79db0) at src/unix/fs.c:1351
>> 1351src/unix/fs.c: No such file or directory.
>> (gdb) s
>> 1357in src/unix/fs.c
>> (gdb) s
>> 1363in src/unix/fs.c
>> (gdb) s
>> 1360in src/unix/fs.c
>> (gdb) s
>> 1361in src/unix/fs.c
>> (gdb) s
>> 1363in src/unix/fs.c
>> (gdb) s
>> 1366in src/unix/fs.c
>> (gdb) s
>> 1367in src/unix/fs.c
>> (gdb)
>> uv__free (ptr=0x0) at src/uv-common.c:78
>> 78  src/uv-common.c: No such file or directory.
>> (gdb)
>> 84  in src/uv-common.c
>> (gdb)
>> __errno_location () at ../csu/errno-loc.c:26
>> 26  ../csu/errno-loc.c: No such file or directory.
>> (gdb)
>> 27  in ../csu/errno-loc.c
>> (gdb)
>> uv__free (ptr=0x0) at src/uv-common.c:85
>> 85  src/uv-common.c: No such file or directory.
>> (gdb)
>> __GI___libc_free (mem=0x0) at malloc.c:2954
>>
>
> This points a lot to a libuv bug.
>
> Now that ilbuv 1.11 is in unstable, can you update and post results here ?
>
> Jérémy
>
>
Using only debian packages (and no npm-installed module) I can't reproduce
the segfault in debian/sid:

dev:~/Software/debian/node-d3-zoom/node-d3-zoom master$ webpack --config
debian/webpack.config.js index.js build/d3-zoom.js --target=web
--output-library=d3-zoom --output-library-target=umd --module-bind
'js=babel-loader'
Hash: 60d4e6b8ef886259fd80
Version: webpack 3.5.6
Time: 2042ms
 AssetSize  Chunks Chunk Names
d3-zoom.js  174 kB   0  [emitted]  main
   [0] /usr/lib/nodejs/d3-selection/lib/index.js 3.28 kB {0} [built]
   [6] /usr/lib/nodejs/d3-interpolate/lib/index.js 4.29 kB {0} [built]
   [9] /usr/lib/nodejs/d3-dispatch/lib/index.js 370 bytes {0} [built]
  [10] /usr/lib/nodejs/d3-selection/lib/creator.js 926 bytes {0} [built]
  [11] /usr/lib/nodejs/d3-selection/lib/namespace.js 576 bytes {0} [built]
  [16] /usr/lib/nodejs/d3-selection/lib/selector.js 238 bytes {0} [built]
  [17] /usr/lib/nodejs/d3-selection/lib/window.js 299 bytes {0} [built]
  [41] ./src/transform.js 1.35 kB {0} [built]
  [42] ./index.js 131 bytes {0} [built]
  [43] ./src/zoom.js 13.5 kB {0} [built]
  [45] /usr/lib/nodejs/d3-drag/lib/index.js 670 bytes {0} [built]
  [94] /usr/lib/nodejs/d3-transition/lib/index.js 854 bytes {0} [built]
 [128] ./src/constant.js 73 bytes {0} [built]
 [129] ./src/event.js 136 bytes {0} [built]
 [130] ./src/noevent.js 204 bytes {0} [built]
+ 116 hidden modules

WARNING in ./src/zoom.js
235:4-11 "export 'default' (imported as 'noevent') was not found in
'./noevent'

WARNING in ./src/zoom.js
260:6-13 "export 'default' (imported as 'noevent') was not found in
'./noevent'

WARNING in ./src/zoom.js
272:6-13 "export 'default' (imported as 'noevent') was not found in
'./noevent'

WARNING in ./src/zoom.js
285:4-11 "export 'default' (imported as 'noevent') was not found in
'./noevent'

WARNING in ./src/zoom.js
335:4-11 "export 'default' (imported as 'noevent') was not found in
'./noevent'

WARNING in ./src/zoom.js
377:74-82 "export 'default' (imported as 'constant') was not found in
'./constant'

Bug#878674: [Pkg-javascript-devel] Bug#878674: Bug#878674: Bug#878674: Bug#878674: Bug#878674: Bug#878674: nodejs segfaults when building d3-* with webpack

2017-11-07 Thread Jérémy Lal 
2017-10-25 16:04 GMT+02:00 Pirate Praveen :

> On ബുധന്‍ 25 ഒക്ടോബര്‍ 2017 07:08 വൈകു, Pirate Praveen wrote:
> > I can reach the segfaulting point faster by setting break point at
> > thread creation
> >
> > b pthread_create.c:333
> >
> > after 8 c, I reach the segfault point.
> >
> >
> >
>
> hopefully more useful bt
>
> (gdb) bt
> #0  node::fs_req_wrap::~fs_req_wrap (this=,
> __in_chrg=) at ../src/node_file.cc:334
> #1  node::Open (args=...) at ../src/node_file.cc:1063
> #2  0x3b905decccb8 in ?? ()
> #3  0x7fff8fc7a418 in ?? ()
> #4  0x7fff8fc7a468 in ?? ()
> #5  0x0003 in ?? ()
> #6  0x in ?? ()
> (gdb) s
> node::Open (args=...) at ../src/node_file.cc:1064
> 1064in ../src/node_file.cc
> (gdb) bt
> #0  node::Open (args=...) at ../src/node_file.cc:1064
> #1  0x3b905decccb8 in ?? ()
> #2  0x7fff8fc7a418 in ?? ()
> #3  0x7fff8fc7a468 in ?? ()
> #4  0x0003 in ?? ()
> #5  0x in ?? ()
> (gdb) s
> v8::ReturnValue::Set (i=, this=)
> at ../src/node_file.cc:1064
> 1064in ../src/node_file.cc
> (gdb) s
> v8::internal::Internals::IntToSmi (value=)
> at ../src/node_file.cc:1064
> 1064in ../src/node_file.cc
> (gdb) s
> v8::internal::SmiTagging<8ul>::IntToSmi (value=)
> at ../src/node_file.cc:1064
> 1064in ../src/node_file.cc
> (gdb) s
> v8::internal::IntToSmi<31> (value=)
> at ../deps/v8/include/v8.h:7274
> 7274../deps/v8/include/v8.h: No such file or directory.
> (gdb) s
> node::Open (args=...) at ../src/node_file.cc:1063
> 1063../src/node_file.cc: No such file or directory.
> (gdb) s
> node::fs_req_wrap::~fs_req_wrap (this=0x7fff8fc79db0,
> __in_chrg=) at ../src/node_file.cc:334
> 334 in ../src/node_file.cc
> (gdb) s
> uv_fs_req_cleanup (req=req@entry=0x7fff8fc79db0) at src/unix/fs.c:1351
> 1351src/unix/fs.c: No such file or directory.
> (gdb) s
> 1357in src/unix/fs.c
> (gdb) s
> 1363in src/unix/fs.c
> (gdb) s
> 1360in src/unix/fs.c
> (gdb) s
> 1361in src/unix/fs.c
> (gdb) s
> 1363in src/unix/fs.c
> (gdb) s
> 1366in src/unix/fs.c
> (gdb) s
> 1367in src/unix/fs.c
> (gdb)
> uv__free (ptr=0x0) at src/uv-common.c:78
> 78  src/uv-common.c: No such file or directory.
> (gdb)
> 84  in src/uv-common.c
> (gdb)
> __errno_location () at ../csu/errno-loc.c:26
> 26  ../csu/errno-loc.c: No such file or directory.
> (gdb)
> 27  in ../csu/errno-loc.c
> (gdb)
> uv__free (ptr=0x0) at src/uv-common.c:85
> 85  src/uv-common.c: No such file or directory.
> (gdb)
> __GI___libc_free (mem=0x0) at malloc.c:2954
>

This points a lot to a libuv bug.

Now that ilbuv 1.11 is in unstable, can you update and post results here ?

Jérémy

Bug#878674: [Pkg-javascript-devel] Bug#878674: Bug#878674: Bug#878674: Bug#878674: Bug#878674: Bug#878674: nodejs segfaults when building d3-* with webpack

2017-10-25 Thread Pirate Praveen 
On ബുധന്‍ 25 ഒക്ടോബര്‍ 2017 07:08 വൈകു, Pirate Praveen wrote:
> I can reach the segfaulting point faster by setting break point at
> thread creation
> 
> b pthread_create.c:333
> 
> after 8 c, I reach the segfault point.
> 
> 
> 

hopefully more useful bt

(gdb) bt
#0  node::fs_req_wrap::~fs_req_wrap (this=,
__in_chrg=) at ../src/node_file.cc:334
#1  node::Open (args=...) at ../src/node_file.cc:1063
#2  0x3b905decccb8 in ?? ()
#3  0x7fff8fc7a418 in ?? ()
#4  0x7fff8fc7a468 in ?? ()
#5  0x0003 in ?? ()
#6  0x in ?? ()
(gdb) s
node::Open (args=...) at ../src/node_file.cc:1064
1064in ../src/node_file.cc
(gdb) bt
#0  node::Open (args=...) at ../src/node_file.cc:1064
#1  0x3b905decccb8 in ?? ()
#2  0x7fff8fc7a418 in ?? ()
#3  0x7fff8fc7a468 in ?? ()
#4  0x0003 in ?? ()
#5  0x in ?? ()
(gdb) s
v8::ReturnValue::Set (i=, this=)
at ../src/node_file.cc:1064
1064in ../src/node_file.cc
(gdb) s
v8::internal::Internals::IntToSmi (value=)
at ../src/node_file.cc:1064
1064in ../src/node_file.cc
(gdb) s
v8::internal::SmiTagging<8ul>::IntToSmi (value=)
at ../src/node_file.cc:1064
1064in ../src/node_file.cc
(gdb) s
v8::internal::IntToSmi<31> (value=)
at ../deps/v8/include/v8.h:7274
7274../deps/v8/include/v8.h: No such file or directory.
(gdb) s
node::Open (args=...) at ../src/node_file.cc:1063
1063../src/node_file.cc: No such file or directory.
(gdb) s
node::fs_req_wrap::~fs_req_wrap (this=0x7fff8fc79db0,
__in_chrg=) at ../src/node_file.cc:334
334 in ../src/node_file.cc
(gdb) s
uv_fs_req_cleanup (req=req@entry=0x7fff8fc79db0) at src/unix/fs.c:1351
1351src/unix/fs.c: No such file or directory.
(gdb) s
1357in src/unix/fs.c
(gdb) s
1363in src/unix/fs.c
(gdb) s
1360in src/unix/fs.c
(gdb) s
1361in src/unix/fs.c
(gdb) s
1363in src/unix/fs.c
(gdb) s
1366in src/unix/fs.c
(gdb) s
1367in src/unix/fs.c
(gdb)
uv__free (ptr=0x0) at src/uv-common.c:78
78  src/uv-common.c: No such file or directory.
(gdb)
84  in src/uv-common.c
(gdb)
__errno_location () at ../csu/errno-loc.c:26
26  ../csu/errno-loc.c: No such file or directory.
(gdb)
27  in ../csu/errno-loc.c
(gdb)
uv__free (ptr=0x0) at src/uv-common.c:85
85  src/uv-common.c: No such file or directory.
(gdb)
__GI___libc_free (mem=0x0) at malloc.c:2954
2954malloc.c: No such file or directory.
(gdb)
2955in malloc.c
(gdb)
2961in malloc.c
(gdb)
uv__free (ptr=0x0) at src/uv-common.c:86
86  src/uv-common.c: No such file or directory.
(gdb)
87  in src/uv-common.c
(gdb)
uv_fs_req_cleanup (req=req@entry=0x7fff8fc79db0) at src/unix/fs.c:1368
1368src/unix/fs.c: No such file or directory.
(gdb)
1369in src/unix/fs.c
(gdb)
node::Open (args=...) at ../src/node_file.cc:1055
1055../src/node_file.cc: No such file or directory.
(gdb)
node::BufferValue::~BufferValue (this=0x7fff8fc79f70,
__in_chrg=) at ../src/node_file.cc:1055
1055in ../src/node_file.cc
(gdb)
node::MaybeStackBuffer::~MaybeStackBuffer
(this=0x7fff8fc79f70,
__in_chrg=) at ../src/util.h:342
342 ../src/util.h: No such file or directory.
(gdb)
node::Open (args=...) at ../src/node_file.cc:1066
1066../src/node_file.cc: No such file or directory.
(gdb)

Thread 1 "node" received signal SIGSEGV, Segmentation fault.
0x3b905df9db8d in ?? ()



signature.asc
Description: OpenPGP digital signature

Bug#878674: [Pkg-javascript-devel] Bug#878674: Bug#878674: Bug#878674: Bug#878674: Bug#878674: nodejs segfaults when building d3-* with webpack

2017-10-25 Thread Pirate Praveen 
I can reach the segfaulting point faster by setting break point at
thread creation

b pthread_create.c:333

after 8 c, I reach the segfault point.



signature.asc
Description: OpenPGP digital signature

Bug#878674: [Pkg-javascript-devel] Bug#878674: Bug#878674: Bug#878674: Bug#878674: nodejs segfaults when building d3-* with webpack

2017-10-25 Thread Pirate Praveen 
On Mon, 16 Oct 2017 21:06:34 +0530 Pirate Praveen
 wrote:
> On തിങ്കള്‍ 16 ഒക്ടോബര്‍ 2017 08:54 വൈകു, Jérémy Lal wrote:
> > 
> > Can you attach the whole failing sbuild log please ?
> >Attached.
> 
> The diff between the current git master and local build is also attached
> (just enabling webpack).

I tried to reach the segfault point in steps and this is what I can
share. Hope this is useful.

(gdb) s
open (__oflag=524288,
__path=0x7fff163d0ca0 "/usr/lib/nodejs/d3-dispatch/package.json")
at /usr/include/x86_64-linux-gnu/bits/fcntl2.h:59
59return __open_alias (__path, __oflag, __va_arg_pack ());
(gdb) s
open64 () at ../sysdeps/unix/syscall-template.S:84
84  ../sysdeps/unix/syscall-template.S: No such file or directory.
(gdb) s
__pthread_enable_asynccancel ()
at ../sysdeps/unix/sysv/linux/x86_64/cancellation.S:59
59  ../sysdeps/unix/sysv/linux/x86_64/cancellation.S: No such file or
directory.
(gdb) s
60  in ../sysdeps/unix/sysv/linux/x86_64/cancellation.S
(gdb) s
61  in ../sysdeps/unix/sysv/linux/x86_64/cancellation.S
(gdb) s
62  in ../sysdeps/unix/sysv/linux/x86_64/cancellation.S
(gdb) s
63  in ../sysdeps/unix/sysv/linux/x86_64/cancellation.S
(gdb) s
65  in ../sysdeps/unix/sysv/linux/x86_64/cancellation.S
(gdb) s
67  in ../sysdeps/unix/sysv/linux/x86_64/cancellation.S
(gdb) s
69  in ../sysdeps/unix/sysv/linux/x86_64/cancellation.S
(gdb) s
70  in ../sysdeps/unix/sysv/linux/x86_64/cancellation.S
(gdb) s
71  in ../sysdeps/unix/sysv/linux/x86_64/cancellation.S
(gdb) c
Continuing.

Thread 1 "node" hit Breakpoint 10, uv__fs_open (req=0x7fff163d0a30)
at src/unix/fs.c:260
260 src/unix/fs.c: No such file or directory.
(gdb) s
open (__oflag=524288, __path=0x7fff163d0c00 "/usr/lib/nodejs/package.json")
at /usr/include/x86_64-linux-gnu/bits/fcntl2.h:59
59return __open_alias (__path, __oflag, __va_arg_pack ());
(gdb) c
Continuing.

Thread 1 "node" hit Breakpoint 10, uv__fs_open (req=0x7fff163d09f0)
at src/unix/fs.c:260
260 src/unix/fs.c: No such file or directory.
(gdb) s
open (__oflag=524288,
__path=0x7fff163d0bc0 "/usr/lib/nodejs/d3-dispatch/package.json")
at /usr/include/x86_64-linux-gnu/bits/fcntl2.h:59
59return __open_alias (__path, __oflag, __va_arg_pack ());
(gdb) c
Continuing.

Thread 1 "node" hit Breakpoint 10, uv__fs_open (req=0x7fff163d09f0)
at src/unix/fs.c:260
260 src/unix/fs.c: No such file or directory.
(gdb) s
open (__oflag=524288, __path=0x7fff163d0bc0 "/usr/lib/nodejs/package.json")
at /usr/include/x86_64-linux-gnu/bits/fcntl2.h:59
59return __open_alias (__path, __oflag, __va_arg_pack ());
(gdb) bt
#0  open (__oflag=524288, __path=0x7fff163d0bc0
"/usr/lib/nodejs/package.json")
at /usr/include/x86_64-linux-gnu/bits/fcntl2.h:59
#1  uv__fs_open (req=0x7fff163d09f0) at src/unix/fs.c:260
#2  uv__fs_work (w=w@entry=0x7fff163d0b40) at src/unix/fs.c:960
#3  0x7f84705bc8f1 in uv_fs_open (
loop=0x7f84707d1c40 ,
req=req@entry=0x7fff163d09f0,
path=, flags=flags@entry=0, mode=mode@entry=438,
cb=cb@entry=0x0) at src/unix/fs.c:1179
#4  0x00d9457c in node::Open (args=...) at ../src/node_file.cc:1063
#5  0x2e9c4e594f78 in ?? ()
#6  0x7fff163d1058 in ?? ()
#7  0x7fff163d10a8 in ?? ()
#8  0x0003 in ?? ()
#9  0x in ?? ()
(gdb) c
Continuing.
[Switching to Thread 0x7f846a5b1700 (LWP 4944)]

Thread 7 "node" hit Breakpoint 10, uv__fs_open (req=0x1f5d948)
at src/unix/fs.c:260
260 src/unix/fs.c: No such file or directory.
(gdb) s
[Switching to Thread 0x7f8470bd9740 (LWP 4275)]

Thread 1 "node" hit Breakpoint 10, uv__fs_open (req=0x7fff163d0ad0)
at src/unix/fs.c:260
260 in src/unix/fs.c
(gdb) s
[Switching to Thread 0x7f8468dae700 (LWP 4947)]

Thread 10 "node" hit Breakpoint 10, uv__fs_open (req=0x1f5caf8)
at src/unix/fs.c:260
260 in src/unix/fs.c
(gdb) s
open (__oflag=524288,
__path=0x1f8d210 "/usr/lib/nodejs/d3-selection/package.json")
at /usr/include/x86_64-linux-gnu/bits/fcntl2.h:59
59return __open_alias (__path, __oflag, __va_arg_pack ());
(gdb) c
Continuing.
[Switching to Thread 0x7f8470bd9740 (LWP 4275)]

Thread 1 "node" hit Breakpoint 10, uv__fs_open (req=0x7fff163d09f0)
at src/unix/fs.c:260
260 src/unix/fs.c: No such file or directory.
(gdb) c
Continuing.

Thread 1 "node" hit Breakpoint 10, uv__fs_open (req=0x7fff163d09f0)
at src/unix/fs.c:260
260 in src/unix/fs.c
(gdb) s
open (__oflag=524288, __path=0x7fff163d0bc0 "/usr/lib/nodejs/package.json")
at /usr/include/x86_64-linux-gnu/bits/fcntl2.h:59
59return __open_alias (__path, __oflag, __va_arg_pack ());
(gdb) c
Continuing.
[Switching to Thread 0x7f846a5b1700 (LWP 4944)]

Thread 7 "node" hit Breakpoint 10, uv__fs_open (req=0x1f88458)
at src/unix/fs.c:260
260 src/unix/fs.c: No such file or directory.
(gdb) s
open (__oflag=524288, __path=0x1f5b8a0

Bug#878674: [Pkg-javascript-devel] Bug#878674: Bug#878674: Bug#878674: Bug#878674: nodejs segfaults when building d3-* with webpack

2017-10-16 Thread Jérémy Lal 
2017-10-16 17:17 GMT+02:00 Pirate Praveen :

> On തിങ്കള്‍ 16 ഒക്ടോബര്‍ 2017 07:13 വൈകു, Jérémy Lal wrote:
> > A memory allocation failure... is it possible you ran out of memory ?
>
> Very unlikely, I have 16 GB ram.
>
> > Anyway i tried typing the same commands as in debian/rules of
> node-d3-zoom,
> > but this time using webpack, babel-cli, babel-loader installed from
> > npmjs.org :
> > no segfault.
>
> So it could be one of the dependencies misbehaving, but we need to find
> out which one.
>

Can you attach the whole failing sbuild log please ?

Bug#878674: [Pkg-javascript-devel] Bug#878674: Bug#878674: Bug#878674: Bug#878674: nodejs segfaults when building d3-* with webpack

2017-10-16 Thread Pirate Praveen 
On തിങ്കള്‍ 16 ഒക്ടോബര്‍ 2017 07:13 വൈകു, Jérémy Lal wrote:
> A memory allocation failure... is it possible you ran out of memory ?

Very unlikely, I have 16 GB ram.

> Anyway i tried typing the same commands as in debian/rules of node-d3-zoom,
> but this time using webpack, babel-cli, babel-loader installed from
> npmjs.org :
> no segfault.

So it could be one of the dependencies misbehaving, but we need to find
out which one.




signature.asc
Description: OpenPGP digital signature

Bug#878674: [Pkg-javascript-devel] Bug#878674: Bug#878674: Bug#878674: nodejs segfaults when building d3-* with webpack

2017-10-16 Thread Jérémy Lal 
2017-10-16 13:10 GMT+02:00 Pirate Praveen :

> On 10/16/2017 04:32 PM, Pirate Praveen wrote:
> > I'm using libuv1 1.11 (built locally) and still seeing the segfault, I
> > think more dbgsym packages need to be installed.
>
> after zlib1g-dbg installed
>
> (gdb) bt
> #0  0x18df10069fc8 in ?? ()
> #1  0x18df105deecf in ?? ()
> #2  0x00bcff01 in v8::internal::NewArray (
> size=) at ../deps/v8/src/allocation.h:60
> #3  v8::internal::SlotSet::AllocateBucket (this=)
> at ../deps/v8/src/heap/slot-set.h:183


A memory allocation failure... is it possible you ran out of memory ?

Anyway i tried typing the same commands as in debian/rules of node-d3-zoom,
but this time using webpack, babel-cli, babel-loader installed from
npmjs.org:
no segfault.

Also note that the the nodejs tests are green here:
https://ci.debian.net/packages/n/nodejs/unstable/amd64/

Jérémy

Bug#878674: [Pkg-javascript-devel] Bug#878674: Bug#878674: Bug#878674: nodejs segfaults when building d3-* with webpack

2017-10-16 Thread Pirate Praveen 
On 10/16/2017 04:32 PM, Pirate Praveen wrote:
> I'm using libuv1 1.11 (built locally) and still seeing the segfault, I
> think more dbgsym packages need to be installed.

after zlib1g-dbg installed

(gdb) bt
#0  0x18df10069fc8 in ?? ()
#1  0x18df105deecf in ?? ()
#2  0x00bcff01 in v8::internal::NewArray (
size=) at ../deps/v8/src/allocation.h:60
#3  v8::internal::SlotSet::AllocateBucket (this=)
at ../deps/v8/src/heap/slot-set.h:183
#4  v8::internal::SlotSet::Insert (slot_offset=,
this=) at ../deps/v8/src/heap/slot-set.h:44
#5  v8::internal::RememberedSet<(v8::internal::PointerDirection)1>::Insert (
slot_addr=, page=)
at ../deps/v8/src/heap/remembered-set.h:29
#6  v8::internal::Heap::RecordWrite (this=, o=,
offset=, object=)
at ../deps/v8/src/heap/heap-inl.h:410
#7  v8::internal::FixedArray::set (value=,
index=, this=)
at ../deps/v8/src/objects-inl.h:2326
#8  v8::internal::FixedArrayBuilder::Add (value=,
this=0x3cfad4d043c9) at ../deps/v8/src/string-builder.h:159
#9  v8::internal::ReplacementStringBuilder::AddElement (
element=, this=0x3cfad4d043c1)
at ../deps/v8/src/string-builder.h:259
#10 v8::internal::ReplacementStringBuilder::AddString (string=...,
---Type  to continue, or q  to quit---
this=0x3cfad4d043c1) at ../deps/v8/src/string-builder.h:235
#11 v8::internal::CompiledReplacement::Apply (this=0x15017c8,
builder=0x3cfad4d043c1, match_from=12386049, match_to=0,
match=0x18df105deecf) at ../deps/v8/src/runtime/runtime-regexp.cc:274
#12 0x18df10587790 in ?? ()
#13 0x0028 in ?? ()
#14 0x34c3f98db741 in ?? ()
#15 0x0002 in ?? ()
#16 0x7fff9458 in ?? ()
#17 0x7fff9440 in ?? ()
#18 0x18df0fd092a7 in ?? ()
#19 0x37ff43bc3dc9 in ?? ()
#20 0x3cfad4d043c1 in ?? ()
#21 0x007d680a9191 in ?? ()
#22 0x0028 in ?? ()
#23 0x34366fe47d59 in ?? ()
#24 0x0423c28cffa1 in ?? ()
#25 0x37ff43bc7669 in ?? ()
#26 0x0423c28cffa1 in ?? ()
#27 0x7fff9498 in ?? ()
#28 0x18df103d9e1d in ?? ()
#29 0x34c3f98db741 in ?? ()
#30 0x37ff43bc7669 in ?? ()
---Type  to continue, or q  to quit---
#31 0x34c3f98dd471 in ?? ()
#32 0x37ff43bbe529 in ?? ()
#33 0x0423c28c6471 in ?? ()
#34 0x7fff94d8 in ?? ()
#35 0x18df0fd09895 in ?? ()
#36 0x3cfad4d04381 in ?? ()
#37 0x3cfad4d043c1 in ?? ()
#38 0x34c3f98db741 in ?? ()
#39 0x0001 in ?? ()
#40 0x37ff43bbe529 in ?? ()
#41 0x000e in ?? ()
#42 0x7fff9578 in ?? ()
#43 0x18df103d4023 in ?? ()
#44 0x3cfad4d043c1 in ?? ()
#45 0x34c3f98db741 in ?? ()
#46 0x37ff43bbe529 in ?? ()
#47 0x34c3f98dd3b9 in ?? ()
#48 0x3cfad4d04271 in ?? ()
#49 0x0001 in ?? ()
#50 0x3cfad4d04381 in ?? ()
#51 0x3cfad4d04381 in ?? ()
#52 0x3cfad4d04271 in ?? ()
#53 0x3cfad4d04381 in ?? ()
---Type  to continue, or q  to quit---
#54 0x3cfad4d04381 in ?? ()
#55 0x3cfad4d04381 in ?? ()
#56 0x3cfad4d04381 in ?? ()
#57 0x3cfad4d04381 in ?? ()
#58 0x3cfad4d04381 in ?? ()
#59 0x34c3f98dd3b9 in ?? ()
#60 0x37ff43bbd539 in ?? ()
#61 0x0423c28c6471 in ?? ()
#62 0x7fff95c8 in ?? ()
#63 0x18df0fd09895 in ?? ()
#64 0x3cfad4d04381 in ?? ()
#65 0x34c3f98dceb1 in ?? ()
#66 0x000f in ?? ()
#67 0x34c3f98dd219 in ?? ()
#68 0x34c3f98db741 in ?? ()
#69 0x0003 in ?? ()
#70 0x37ff43bbd539 in ?? ()
#71 0x000e in ?? ()
#72 0x7fff9638 in ?? ()
#73 0x18df103cfce5 in ?? ()
#74 0x34c3f98dceb1 in ?? ()
#75 0x000f in ?? ()
#76 0x34c3f98dd219 in ?? ()
---Type  to continue, or q  to quit---
#77 0x34c3f98db741 in ?? ()
#78 0x37ff43bbd539 in ?? ()
#79 0x3cfad4d04429 in ?? ()
#80 0x3cfad4d04271 in ?? ()
#81 0x34c3f98dd219 in ?? ()
#82 0x34c3f98dceb1 in ?? ()
#83 0x000f in ?? ()
#84 0x37ff43bbd489 in ?? ()
#85 0x0423c28c6471 in ?? ()
#86 0x7fff96a0 in ?? ()
#87 0x18df103cf470 in ?? ()
#88 0x34c3f98dd1e1 in ?? ()
#89 0x34c3f98db741 in ?? ()
#90 0x37ff43bbd489 in ?? ()
#91 0x3cfad4d04381 in ?? ()
#92 0x34c3f98dceb1 in ?? ()
#93 0x000f in ?? ()
#94 0x3cfad4d04381 in ?? ()
#95 0x3cfad4d04381 in ?? ()
#96 0x3cfad4d04381 in ?? ()
#97 0x37ff43bbd3d9 in ?? ()
#98 0x0423c28c6471 in ?? ()
#99 0x7fff96f8 in ?? ()
---Type  to continue, or q  to quit---
#100 0x18df105ab3e8 in ?? ()
#101 0x3cfad4d04271 in ?? ()
#102 0x34c3f98dd1e1 in ?? ()
#103 0x34c3f98db741 in ?? ()
#104 0x3cfad4d04381 in ?? ()
#105 0x34c3f98dceb1 in ?? ()
#106 0x000f in ?? ()
#107 0x0423c28c6471 in ?? ()
#108 0x37ff43bbd1c9 in ?? ()
#109 0x0423c28c6471 in ?? ()
#110 0x7fff9758 in ?? ()
#111 0x18df103ce6be in ?? ()
#112 0x34c3f98dd1e1 in ?? ()
#113 0x3cfad4d04381 in ?? ()
#114 0x34c3f98db741 in ??

Bug#878674: [Pkg-javascript-devel] Bug#878674: Bug#878674: nodejs segfaults when building d3-* with webpack

2017-10-16 Thread Pirate Praveen 
On 10/16/2017 03:21 PM, Jérémy Lal wrote:
> 
> Update: i uploaded libuv1 1.11.0 to experimental.
> I strongly suspect the bug you see will be fixed with that version.
> 
> Jérémy

I'm using libuv1 1.11 (built locally) and still seeing the segfault, I
think more dbgsym packages need to be installed.

(gdb) bt
#0  0x2fe38955cd76 in ?? ()
#1  0x40b5c800 in ?? ()
#2  0x15c7 in ?? ()
#3  0x40478000 in ?? ()
#4  0x023b145957053b00 in ?? ()
#5  0x262e40c38fe9 in ?? ()
#6  0x262e40c37d39 in ?? ()
#7  0x0e94d9fc73d9 in ?? ()
#8  0x0929666c22c9 in ?? ()
#9  0x7fff8130 in ?? ()
#10 0x2fe389548c70 in ?? ()
#11 0x002e in ?? ()
#12 0x1117aff862a1 in ?? ()
#13 0x in ?? ()




signature.asc
Description: OpenPGP digital signature

Bug#878674: [Pkg-javascript-devel] Bug#878674: Bug#878674: nodejs segfaults when building d3-* with webpack

2017-10-16 Thread Jérémy Lal 
2017-10-16 11:28 GMT+02:00 Jérémy Lal :

>
>
> 2017-10-16 9:59 GMT+02:00 Pirate Praveen :
>
>> On 10/16/2017 01:18 PM, Jérémy Lal wrote:
>> >
>> >
>> > 2017-10-16 9:43 GMT+02:00 Pirate Praveen > > >:
>> >
>> > On 10/16/2017 12:47 PM, Jérémy Lal wrote:
>> > > You could get a more useful stack trace by installing
>> nodejs-dbgsym
>> > > package from
>> > > deb http://debug.mirrors.debian.org/debian-debug/
>> >  unstable-debug main
>> >
>> > I have installed it, but the output is still the same, no extra
>> details.
>> >
>> >
>> > You're supposed to run node through gdb:
>> >
>> > gdb node
>> >> run

Bug#878674: [Pkg-javascript-devel] Bug#878674: Bug#878674: nodejs segfaults when building d3-* with webpack

2017-10-16 Thread Jérémy Lal 
2017-10-16 9:59 GMT+02:00 Pirate Praveen :

> On 10/16/2017 01:18 PM, Jérémy Lal wrote:
> >
> >
> > 2017-10-16 9:43 GMT+02:00 Pirate Praveen  > >:
> >
> > On 10/16/2017 12:47 PM, Jérémy Lal wrote:
> > > You could get a more useful stack trace by installing nodejs-dbgsym
> > > package from
> > > deb http://debug.mirrors.debian.org/debian-debug/
> >  unstable-debug main
> >
> > I have installed it, but the output is still the same, no extra
> details.
> >
> >
> > You're supposed to run node through gdb:
> >
> > gdb node
> >> run

Bug#878674: [Pkg-javascript-devel] Bug#878674: Bug#878674: nodejs segfaults when building d3-* with webpack

2017-10-16 Thread Pirate Praveen 
On 10/16/2017 01:18 PM, Jérémy Lal wrote:
> 
> 
> 2017-10-16 9:43 GMT+02:00 Pirate Praveen  >:
> 
> On 10/16/2017 12:47 PM, Jérémy Lal wrote:
> > You could get a more useful stack trace by installing nodejs-dbgsym
> > package from
> > deb http://debug.mirrors.debian.org/debian-debug/
>  unstable-debug main
> 
> I have installed it, but the output is still the same, no extra details.
> 
> 
> You're supposed to run node through gdb:
> 
> gdb node
>> run

Bug#878674: [Pkg-javascript-devel] Bug#878674: Bug#878674: nodejs segfaults when building d3-* with webpack

2017-10-16 Thread Jérémy Lal 
2017-10-16 9:43 GMT+02:00 Pirate Praveen :

> On 10/16/2017 12:47 PM, Jérémy Lal wrote:
> > You could get a more useful stack trace by installing nodejs-dbgsym
> > package from
> > deb http://debug.mirrors.debian.org/debian-debug/ unstable-debug main
>
> I have installed it, but the output is still the same, no extra details.
>
>
You're supposed to run node through gdb:

gdb node
> run

Bug#878674: [Pkg-javascript-devel] Bug#878674: Bug#878674: nodejs segfaults when building d3-* with webpack

2017-10-16 Thread Pirate Praveen 
On 10/16/2017 12:47 PM, Jérémy Lal wrote:
> You could get a more useful stack trace by installing nodejs-dbgsym
> package from
> deb http://debug.mirrors.debian.org/debian-debug/ unstable-debug main

I have installed it, but the output is still the same, no extra details.



signature.asc
Description: OpenPGP digital signature

Bug#878674: [Pkg-javascript-devel] Bug#878674: Bug#878674: nodejs segfaults when building d3-* with webpack

2017-10-16 Thread Pirate Praveen 
On 10/16/2017 12:47 PM, Jérémy Lal wrote:
> You could get a more useful stack trace by installing nodejs-dbgsym
> package from
> deb http://debug.mirrors.debian.org/debian-debug/ unstable-debug main
> 
> Jérémy

I will try that,

meanwhile I tried,
 NODE_PATHocal/lib/node_modules node debug
/usr/lib/nodejs/webpack/bin/webpack.js --config debian/webpack.config.js
index.js build/d3-zoom.js --target=web --output-library=d3-zoom
--output-library-target=umd --module-bind 'js=babel-loader'

and found the line that is causing segfault.

break in /usr/lib/nodejs/babel-loader/lib/index.js:168
 166   const { code, map, metadata } = transpile(source, options);
 167
>168   metadataSubscribers.forEach(s => passMetadata(s, this, metadata));
 169
 170   this.callback(null, code, map);
debug>
break in /usr/lib/nodejs/babel-loader/lib/index.js:170
 168   metadataSubscribers.forEach(s => passMetadata(s, this, metadata));
 169
>170   this.callback(null, code, map);
 171 };
 172 });
debug>
< PID 22632 received SIGSEGV for address: 0x0
<
/usr/local/lib/node_modules/segfault-handler/build/Release/segfault-handler.node(+0x199c)[0x7fec0788b99c]
< /lib/x86_64-linux-gnu/libpthread.so.0(+0x110c0)[0x7fec0a8580c0]
< [0x7a34cf7e628]




signature.asc
Description: OpenPGP digital signature

Bug#878674: [Pkg-javascript-devel] Bug#878674: Bug#878674: nodejs segfaults when building d3-* with webpack

2017-10-16 Thread Jérémy Lal 
2017-10-16 8:54 GMT+02:00 Pirate Praveen :

> On 10/16/2017 10:32 AM, Pirate Praveen wrote:
> > I don't think any of them is a C++ addon, probably one of their
> > dependencies.
> >
> >
> >
>
> After using segfault-handler node module, I get this message,
>
> PID 21070 received SIGSEGV for address: 0x0
> /usr/local/lib/node_modules/segfault-handler/build/
> Release/segfault-handler.node(+0x1a0d)[0x7f54aad48a0d]
> /lib/x86_64-linux-gnu/libpthread.so.0(+0x110c0)[0x7f54ad5140c0]
> [0x368109d6c128]
>
> npm install -g segfault-handler
>
> and add export NODE_PATH=/usr/local/lib/node_modules in debian/rules
>
> and add these two lines to /usr/lib/nodejs/webpack/bin/webpack.js
>
> var SegfaultHandler = require('segfault-handler');
>
> SegfaultHandler.registerHandler("crash.log");
>

You could get a more useful stack trace by installing nodejs-dbgsym package
from
deb http://debug.mirrors.debian.org/debian-debug/ unstable-debug main

Jérémy

Bug#878674: [Pkg-javascript-devel] Bug#878674: Bug#878674: nodejs segfaults when building d3-* with webpack

2017-10-16 Thread Pirate Praveen 
On 10/16/2017 10:32 AM, Pirate Praveen wrote:
> I don't think any of them is a C++ addon, probably one of their
> dependencies.
> 
> 
> 

After using segfault-handler node module, I get this message,

PID 21070 received SIGSEGV for address: 0x0
/usr/local/lib/node_modules/segfault-handler/build/Release/segfault-handler.node(+0x1a0d)[0x7f54aad48a0d]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x110c0)[0x7f54ad5140c0]
[0x368109d6c128]

npm install -g segfault-handler

and add export NODE_PATH=/usr/local/lib/node_modules in debian/rules

and add these two lines to /usr/lib/nodejs/webpack/bin/webpack.js

var SegfaultHandler = require('segfault-handler');

SegfaultHandler.registerHandler("crash.log");



signature.asc
Description: OpenPGP digital signature

Bug#878674: [Pkg-javascript-devel] Bug#878674: nodejs segfaults when building d3-* with webpack

2017-10-15 Thread Pirate Praveen 
On ഞായര്‍ 15 ഒക്ടോബര്‍ 2017 11:39 വൈകു, Jérémy Lal wrote:
> Do you know if any dependency is a c++ addon ?

These are the direct dependencies,

Depends:
 ${misc:Depends}
 , nodejs
 , node-acorn (>= 5.0~)
 , node-acorn-dynamic-import (>= 2.0~)
 , node-ajv (>= 5.0~)
 , node-ajv-keywords (>= 2.0~)
 , node-async (>= 0.8~)
 , node-enhanced-resolve (>= 3.4~)
 , node-escope
 , node-interpret (>= 1.0~)
 , node-json-loader (>= 0.5.4~)
 , node-json5 (>= 0.5~)
 , node-loader-runner (>= 2.3~)
 , node-loader-utils (>= 0.2~)
 , node-memory-fs (>= 0.4.1~)
 , node-mkdirp (>= 0.5~)
 , node-libs-browser (>= 2.0~)
 , node-source-map (>= 0.5.3~)
 , node-supports-color (>= 4.2.1~)
 , node-tapable (>= 0.2.7~)
 , node-uglifyjs-webpack-plugin
 , node-watchpack (>= 1.3.1~)
 , node-webpack-sources (>= 1.0.1~)
 , node-yargs (>= 6.0~)
 , node-lodash-packages
 , node-lodash

I don't think any of them is a C++ addon, probably one of their
dependencies.



signature.asc
Description: OpenPGP digital signature

Bug#878674: nodejs segfaults when building d3-* with webpack

2017-10-15 Thread Jérémy Lal 
2017-10-15 18:36 GMT+02:00 Pirate Praveen :

> package: nodejs
> version: 6.11.4~dfsg-1
> severity: serious
>
> I have noticed this failure when building multiple node-d3-* packages
> (node-d3-zoom for example) and also installing gitlab 9.5 using webpack.
>
> When building the same node-d3-zoom with nodejs
> 7.10.1-2nodesource1~stretch1 the build passed. Tried both in local
> installation and using sbuild.
>
> Also tested the same on my laptop and on a vm
>
> babeljs src -d lib
> src/constant.js -> lib/constant.js
> src/event.js -> lib/event.js
> src/noevent.js -> lib/noevent.js
> src/transform.js -> lib/transform.js
> src/zoom.js -> lib/zoom.js
> babeljs index.js -d lib
> index.js -> lib/index.js
> sed -i 's/.\/src/./' lib/index.js
> webpack --config debian/webpack.config.js index.js build/d3-zoom.js
> --target=web --output-library=d3-zoom --output-library-target=umd
> --module-bind 'js=babel-loader'
> debian/rules:12: recipe for target 'override_dh_auto_build' failed
> make[1]: *** [override_dh_auto_build] Segmentation fault
> make[1]: Leaving directory '/<>'
> debian/rules:9: recipe for target 'build' failed
> make: *** [build] Error 2
> dpkg-buildpackage: error: debian/rules build gave error exit status 2
>
>
> Since babel and other dependencies are still in NEW, I have setup a repo
> for packages still in NEW.
>
> I have /usr/local/bin/sbuild-babel,
> sbuild -A -s -d unstable --extra-repository='deb
> https://people.debian.org/~praveen/babel sid main'
> --extra-repository-key=/home/pravi/forge/debian/babel/repo/praveen.key.asc
> $@
>
> With nodejs from nodesource.com, the build passes, both locally and in
> sbuild. For sbuild I have to pass --extra-package option and in
> debian/rules, I have to add export NODE_PATH=/usr/lib/nodejs
>
> node-d3-geo, node-d3-scale are other packages that segfaults.
>
> All node-d3-* packages are in pkg-javascript team repo in alioth.
>
>
Do you know if any dependency is a c++ addon ?

Jérémy

Bug#878674: nodejs segfaults when building d3-* with webpack

2017-10-15 Thread Pirate Praveen 
package: nodejs
version: 6.11.4~dfsg-1
severity: serious

I have noticed this failure when building multiple node-d3-* packages
(node-d3-zoom for example) and also installing gitlab 9.5 using webpack.

When building the same node-d3-zoom with nodejs
7.10.1-2nodesource1~stretch1 the build passed. Tried both in local
installation and using sbuild.

Also tested the same on my laptop and on a vm

babeljs src -d lib
src/constant.js -> lib/constant.js
src/event.js -> lib/event.js
src/noevent.js -> lib/noevent.js
src/transform.js -> lib/transform.js
src/zoom.js -> lib/zoom.js
babeljs index.js -d lib
index.js -> lib/index.js
sed -i 's/.\/src/./' lib/index.js
webpack --config debian/webpack.config.js index.js build/d3-zoom.js
--target=web --output-library=d3-zoom --output-library-target=umd
--module-bind 'js=babel-loader'
debian/rules:12: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Segmentation fault
make[1]: Leaving directory '/<>'
debian/rules:9: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2


Since babel and other dependencies are still in NEW, I have setup a repo
for packages still in NEW.

I have /usr/local/bin/sbuild-babel,
sbuild -A -s -d unstable --extra-repository='deb
https://people.debian.org/~praveen/babel sid main'
--extra-repository-key=/home/pravi/forge/debian/babel/repo/praveen.key.asc
$@

With nodejs from nodesource.com, the build passes, both locally and in
sbuild. For sbuild I have to pass --extra-package option and in
debian/rules, I have to add export NODE_PATH=/usr/lib/nodejs

node-d3-geo, node-d3-scale are other packages that segfaults.

All node-d3-* packages are in pkg-javascript team repo in alioth.



signature.asc
Description: OpenPGP digital signature