You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
segment fault when compile node 0.1x branch with gcc 6.1.1 in 64bit linux #6724
after update gcc version from 5.3 to 6.1.1, the compile of node 0.12.7 failed with segment fault, this issue not happened when compile debug version and i compile 0.12.14 the issue still exist and it disappeared after remove -O3 from makefile.
debug the issue found the reason is: #0 v8::internal::PagedSpace::Contains (addr=0x0, this=0xd61ff0) at ../deps/v8/src/heap/spaces-inl.h:152 152 return p->owner() == this;
the input argument addr is null, after add a check for the input argument, this issue disappear.
Try building with make CXX="g++ -fno-delete-null-pointer-checks". v0.12 is in maintenance mode and close to being EOL'd so I don't think we'll fix this.
Perhaps if we do another v0.12 release (big if), we could add -fno-delete-null-pointer-checks to the default build flags.
Activity
bnoordhuis commentedon May 13, 2016
Try building with
make CXX="g++ -fno-delete-null-pointer-checks". v0.12 is in maintenance mode and close to being EOL'd so I don't think we'll fix this.Perhaps if we do another v0.12 release (big if), we could add
-fno-delete-null-pointer-checksto the default build flags.build: turn on -fno-delete-null-pointer-checks
build: turn on -fno-delete-null-pointer-checks
bnoordhuis commentedon May 13, 2016
I filed #6737 and #6738 for v0.12 and v0.10 respectively.
build: turn on -fno-delete-null-pointer-checks
build: turn on -fno-delete-null-pointer-checks
build: turn on -fno-delete-null-pointer-checks
build: turn on -fno-delete-null-pointer-checks
build: turn on -fno-delete-null-pointer-checks
jasnell commentedon Dec 29, 2016
Closing this given that support for v0.12 is coming to a close in two days and there will not be any further updates to the v0.12 branch.
bnoordhuis commentedon Jan 10, 2017
For posterity: this was fixed in v0.10.47 and v0.12.16, released in September 2016.