IV86746: SEGMENTATION FAULT WITH 64-BIT IBM SDK FOR NODE.JS ON LINUX ON Z SYSTEMS

APAR status

• Closed as program error.

Error description

• Error Message: A segmentation fault resulting in a process
  crash/abend.
  .
  Stack Trace: N/A
  .
  The cause of the segmentation is an invalid pointer that is
  generated by the following sequence, which can be validated from
  a core dump:
  IIHF R0, <upper half of 64-bit const>
  IILF R0, <lower half of 64-bit const>
  SGR Rx, R0, Ry
  ...
  LG/STG Rt, 0(Rx) <=== ABEND happens here due to invalid Rx
  value.
  with Ry being a 32-bit value, and Rx being the invalid pointer
  being used to access memory.
  

Local fix

• The issue can be circumvented by specifying the
  '--no-crankshaft' option that disables v8's JIT, but which will
  also incur a significant performance penalty.
  

Problem summary

• The problem is a missing sign extension of a register operand
  prior to being fed into a subtract operation.  As a result, an
  incorrect difference is calculated for an address by the
  subtraction.
  

Problem conclusion

• The crankshaft JIT compiler within V8 has been fixed to properly
  perform the missing sign extension on this architecture.
  .
  This APAR will be fixed in the following IBM SDK for Node.js
  Releases:
     4.3.1.0
     IBM SDK for Node.js 1.2.0.10
  .
  Contact your IBM Product's Service Team for these Service
  Refreshes and Fix Packs.
  For those running stand-alone, information about the available
  Service Refreshes and Fix Packs can be found at:
             http://www.ibm.com/developerworks/web/nodesdk/
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  NODE.JS

• Fixed component ID

  AIMNDJS00

Applicable component levels

• R421 PSY

     UP

• R120 PSY

     UP