segfault in v0.6.7 on osx lion (possibly in a node_crypto.cc thread pool call?)

[ry]

reported by @derekcollison

~> node -v
v0.6.7
~> which node
/usr/local/bin/node
~> npm
Segmentation fault: 11
~> which npm
/usr/local/bin/npm
~> gdb --args node `which npm` -v
GNU gdb 6.3.50-20050815 (Apple version gdb-1705) (Fri Jul  1 10:50:06 UTC 2011)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "x86_64-apple-darwin"...Reading symbols for shared libraries ........... done

(gdb) r
Starting program: /usr/local/bin/node /usr/local/bin/npm -v
Reading symbols for shared libraries ++++++++++.......................................................................................................................... done

Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_ADDRESS at address: 0x0000000000000950
0x00000001000570e5 in v8::HandleScope::RawClose () at node_crypto.h:166
166     return ss;
(gdb) where
#0  0x00000001000570e5 in v8::HandleScope::RawClose () at node_crypto.h:166
#1  0x0000000100011597 in v8::HandleScope::Close<v8::Object> () at /Users/derek/Downloads/node-v0.6.7/deps/v8/include/v8.h:3953
#2  0x0000000100011597 in Stat (args=@0x7fff5fbff288) at v8.h:343
#3  0x0000000100072f8e in v8::internal::Builtin_HandleApiCall () at node_crypto.h:166
Previous frame inner to this frame (gdb could not unwind past this frame)
(gdb) 

[derekcollison]

> uname -a
Darwin Dereks-iMac.local 11.2.0 Darwin Kernel Version 11.2.0: Tue Aug 9 20:54:00 PDT 2011; root:xnu-1699.24.81/RELEASE_X86_64 x86_64
>
> gcc -v
Using built-in specs.
Target: i686-apple-darwin11
Configured with: /private/var/tmp/llvmgcc42/llvmgcc42-2335.1525/src/configure --disable-checking --enable-werror --prefix=/Developer/usr/llvm-gcc-4.2 --mandir=/share/man --enable-languages=c,objc,c++,obj-c++ --program-prefix=llvm- --program-transform-name=/^[cg][^.-]*$/s/$/-4.2/ --with-slibdir=/usr/lib --build=i686-apple-darwin11 --enable-llvm=/private/var/tmp/llvmgcc42/llvmgcc42-2335.1525/dst-llvmCore/Developer/usr/local --program-prefix=i686-apple-darwin11- --host=x86_64-apple-darwin11 --target=i686-apple-darwin11 --with-gxx-include-dir=/usr/include/c++/4.2.1
Thread model: posix
gcc version 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2335.15.00)
~>
~> gdb -v
GNU gdb 6.3.50-20050815 (Apple version gdb-1705) (Fri Jul 1 10:50:06 UTC 2011)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "x86_64-apple-darwin".

[derekcollison]

I am going to completely blow away Xcode and reinstall..

[bnoordhuis]

@derekcollison: If the crash keeps happening, can you send me your node binary and a core file from the crash? ulimit -c unlimited turns on core dumps.

[derekcollison]

Sure, it seems to be npm that is causing it. Vagrind didn't offer much insight..

I blew away all of Xcode and reinstalled, same thing happens..

On Jan 10, 2012, at 8:49 AM, Ben Noordhuisreply@reply.github.com wrote:

@derekcollison: If the crash keeps happening, can you send me your node binary and a core file from the crash? ulimit -c unlimited turns on core dumps.

---

Reply to this email directly or view it on GitHub:
#2498 (comment)

[derekcollison]

Ben,

Still fairly certain it is my messed up machine, however I uploaded the core from npm -v, along with the node and npm files. You can find them here..

http://dl.dropbox.com/u/7891/NodeIssue/node
http://dl.dropbox.com/u/7891/NodeIssue/npm
http://dl.dropbox.com/u/7891/NodeIssue/core.npm-v.bz2

[davidbanham]

I'm seeing the same behaviour. Node v0.6.8 compiled with the --debug flag

davidbanham@David-Banhams-MacBook-Pro:~/repos/hnymn$ /opt/node/bin/node -v
v0.6.8
davidbanham@David-Banhams-MacBook-Pro:/repos/hnymn$

davidbanham@David-Banhams-MacBook-Pro:~/repos/hnymn$ gdb --args ~/opt/node/bin/node app.js
GNU gdb 6.3.50-20050815 (Apple version gdb-1705) (Fri Jul 1 10:50:06 UTC 2011)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "x86_64-apple-darwin"...Reading symbols for shared libraries ........... done

(gdb) run
Starting program: /Users/davidbanham/opt/node/bin/node app.js
Reading symbols for shared libraries ++++++++++.......................................................................................................................... done
Reading symbols for shared libraries . done

Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_ADDRESS at address: 0x0000007fff5fc00a
0x00000001000fca48 in v8::internal::Isolate::PromoteScheduledException () at node_crypto.h:166
166 return ss;
(gdb)

[davidbanham]

(gdb) backtrace full
#0 0x00000001000fca48 in v8::internal::Isolate::PromoteScheduledException () at node_crypto.h:166
No symbol table info available.
#1 0x0000000100072aed in v8::internal::Builtin_HandleApiCall () at node_crypto.h:166
No symbol table info available.
Previous frame inner to this frame (gdb could not unwind past this frame)
(gdb)

[davidbanham]

davidbanham@David-Banhams-MacBook-Pro:/repos/hnymn$ gcc -v
Using built-in specs.
Target: i686-apple-darwin11
Configured with: /private/var/tmp/llvmgcc42/llvmgcc42-2335.1525/src/configure --disable-checking --enable-werror --prefix=/Developer/usr/llvm-gcc-4.2 --mandir=/share/man --enable-languages=c,objc,c++,obj-c++ --program-prefix=llvm- --program-transform-name=/^[cg][^.-]*$/s/$/-4.2/ --with-slibdir=/usr/lib --build=i686-apple-darwin11 --enable-llvm=/private/var/tmp/llvmgcc42/llvmgcc42-2335.1525/dst-llvmCore/Developer/usr/local --program-prefix=i686-apple-darwin11- --host=x86_64-apple-darwin11 --target=i686-apple-darwin11 --with-gxx-include-dir=/usr/include/c++/4.2.1
Thread model: posix
gcc version 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2335.15.00)
davidbanham@David-Banhams-MacBook-Pro:/repos/hnymn$ gdb -v
GNU gdb 6.3.50-20050815 (Apple version gdb-1705) (Fri Jul 1 10:50:06 UTC 2011)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "x86_64-apple-darwin".

[bnoordhuis]

@derekcollison, @davidbanham: Sorry for the delay. Does it still happen with recent releases?

[derekcollison]

I will check and get back to you..

On Feb 17, 2012, at 6:33 PM, Ben Noordhuisreply@reply.github.com wrote:

@derekcollison, @davidbanham: Sorry for the delay. Does it still happen with recent releases?

---

Reply to this email directly or view it on GitHub:
#2498 (comment)

[derekcollison]

I just installed 0.6.11 and it still happens..

I then install 0.7.4, and that works, no segfault.

I will try to remove Xcode again and go with the newly released command
line tools only to see if it makes a difference..

On Fri, Feb 17, 2012 at 6:33 PM, Ben Noordhuis <
reply@reply.github.com

wrote:

@derekcollison, @davidbanham: Sorry for the delay. Does it still happen
with recent releases?

---

Reply to this email directly or view it on GitHub:
#2498 (comment)

[derekcollison]

Still happens on the 0.6.11 series when using the new command line tools..

/> gcc -v
Using built-in specs.
Target: i686-apple-darwin11
Configured with: /private/var/tmp/llvmgcc42/llvmgcc42-2336.922/src/configure --disable-checking --enable-werror --prefix=/Applications/Xcode.app/Contents/Developer/usr/llvm-gcc-4.2 --mandir=/share/man --enable-languages=c,objc,c++,obj-c++ --program-prefix=llvm- --program-transform-name=/^[cg][^.-]*$/s/$/-4.2/ --with-slibdir=/usr/lib --build=i686-apple-darwin11 --enable-llvm=/private/var/tmp/llvmgcc42/llvmgcc42-2336.9~22/dst-llvmCore/Developer/usr/local --program-prefix=i686-apple-darwin11- --host=x86_64-apple-darwin11 --target=i686-apple-darwin11 --with-gxx-include-dir=/usr/include/c++/4.2.1
Thread model: posix
gcc version 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.9.00)
~/> cc -v
Apple clang version 3.1 (tags/Apple/clang-318.0.45) (based on LLVM 3.1svn)
Target: x86_64-apple-darwin11.3.0
Thread model: posix

[bnoordhuis]

@derekcollison: Thanks. Can you post the output of file out/Release/node for both versions? I'm curious if they're built for different architectures.

[derekcollison]

~/.nvm/v0.6.11/bin> file node
node: Mach-O 64-bit executable x86_64
~/.nvm/v0.6.11/bin> cd ~/.nvm/v0.6.11/bin
~/.nvm/v0.6.11/bin> file node
node: Mach-O 64-bit executable x86_64

[bnoordhuis]

@derekcollison: Are you running file twice on the same binary or am I misreading that?