-
Notifications
You must be signed in to change notification settings - Fork 7.3k
glibc errors on SheevaPlug / Debian Squeeze #3749
Comments
I have no idea what might be causing that. Does it make a difference when you set |
Seeing the same message with v0.8.5 on Arch Linux, running in a Raspberry Pi... |
Pulled down the stable 0.8.6 tarball, and got this error. Ran the test under valgrind, and it seems that we're walking off the end of an array of size 0 down inside of uv_cpu_info() because /proc/cpuinfo is not formatted as expected. Fixing the code (just a sanity check in the loop on numcpus, with a decrement) prevents the crash, but the test still fails (I'm guessing because 0 cpus is something the test does not like). |
@docfaraday Can you post the output of |
FWIW, here's my cpuinfo:
|
@docfaraday Thanks. Continues in joyent/libuv#526. |
This is fixed in joyent/libuv@9a48381. It will be in the next v0.8 release. |
As previously mentioned in issue #2131, I'm having trouble getting node to work on my SheevaPlug with Debian squeeze. I'm working from the latest v0.8 branch checkout, and compiling node using
After this, running the tests results in several glibc errors:
As most of these were in tls/https-related tests I tried passing --shared-openssl to configure. This reduced the number of glibc errors in the tests, but I'm still getting the error in test-os.js. Running this through gdb is unfortunately not very useful, as I seem to be hitting some bug where the stack trace is:
followed by the same abort() all the way down. Any suggestions are very welcome.
The text was updated successfully, but these errors were encountered: