nodejs exits with Illegal instruction

Bug #1320337 reported by Bart Overkamp
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Raspbian
Fix Released
Undecided
Unassigned

Bug Description

# nodejs
Illegal instruction

# nodejs --version
v0.10.26

Installed from official repository in jessie release on Raspberry Pi model B

expected:

nodejs interactive javascript server starts

Any clues to fix this?
I'll try building/compiling the package myself, but due to a lack of cross-compile hosts I'll do it on the pi itself.

Distributor ID: Raspbian
Description: Raspbian GNU/Linux testing (jessie)
Release: testing
Codename: jessie
Architecture: armv6l

Kernel: Linux 3.10.25+ (PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages nodejs depends on:
ii libc-ares2 1.10.0-2
ii libc6 2.18-5
ii libgcc1 1:4.9.0-2
ii libssl1.0.0 1.0.1g-3
ii libstdc++6 4.9.0-2
ii libv8-3.14.5 3.14.5.8-8
ii zlib1g 1:1.2.8.dfsg-1

nodejs recommends no packages.

nodejs suggests no packages.

-- no debconf information

Tags: jessie nodejs v8
gaspard (gaspard)
tags: added: jessie nodejs v8
Revision history for this message
peter green (plugwash) wrote :

Doing some checks in gdb it looks like the v8 JIT is generating movw/movt which are armv7 specific instructions.

Revision history for this message
peter green (plugwash) wrote :

Appears to be a build configuration problem in source package libv8-3.14

Revision history for this message
peter green (plugwash) wrote :

building modified libv8-3.14 package, will test soon but right now it's way past bedtime.

Changed in raspbian:
status: New → In Progress
Revision history for this message
peter green (plugwash) wrote :

A fixed version of the libv8-3.14 source package and associated binary packages has now been uploaded and should hit the public repo in the next update run.

Changed in raspbian:
status: In Progress → Fix Released
Revision history for this message
Bart Overkamp (bart-launchpad-7) wrote :

I can confirm the fix:

root@pi:/home/pi# apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  libv8-3.14-dev libv8-3.14.5
2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 1,160 kB of archives.
After this operation, 64.5 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://mirrordirector.raspbian.org/raspbian/ jessie/main libv8-3.14-dev armhf 3.14.5.8-8+rpi1 [108 kB]
Get:2 http://mirrordirector.raspbian.org/raspbian/ jessie/main libv8-3.14.5 armhf 3.14.5.8-8+rpi1 [1,052 kB]
Fetched 1,160 kB in 0s (1,442 kB/s)
(Reading database ... 42432 files and directories currently installed.)
Preparing to unpack .../libv8-3.14-dev_3.14.5.8-8+rpi1_armhf.deb ...
Unpacking libv8-3.14-dev (3.14.5.8-8+rpi1) over (3.14.5.8-8) ...
Preparing to unpack .../libv8-3.14.5_3.14.5.8-8+rpi1_armhf.deb ...
Unpacking libv8-3.14.5 (3.14.5.8-8+rpi1) over (3.14.5.8-8) ...
Setting up libv8-3.14.5 (3.14.5.8-8+rpi1) ...
Setting up libv8-3.14-dev (3.14.5.8-8+rpi1) ...
Processing triggers for libc-bin (2.18-7) ...
root@pi:/home/pi# nodejs
> console.log("Awesome!")
Awesome!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.