IV26902: SEGMENTATION FAULT IN WALKMETHODFRAME WHEN USING -XTRACE:TRIGGER

APAR status

• Closed as program error.

Error description

• Error Message: N/A
  .
  Stack Trace: walkMethodFrame+0x15 (swalk.c:668, 0x003D8395
  <OSB>j9vm24+0x38395<CSB>)
  walkStackFrames+0x176 (swalk.c:285, 0x003D86D6
  <OSB>j9vm24+0x386d6<CSB>)
  doTriggerActionJstacktrace+0xa7 (trigger.c:2134, 0x00C665A7
  <OSB>j9trc24+0x65a7<CSB>)
  triggerHit+0x5c (trigger.c:2451, 0x00C66A0C
  <OSB>j9trc24+0x6a0c<CSB>)
  twTriggerHit+0x1e (tracewrappers.c:121, 0x00C6103E
  <OSB>j9trc24+0x103e<CSB>)
  utsTraceV+0x11d (ut_trace.c:2115, 0x698AFBBD
  <OSB>j9ute24+0xfbbd<CSB>)
  j9Trace+0x31 (tracewrappers.c:718, 0x00C61B91
  <OSB>j9trc24+0x1b91<CSB>)
  sun_misc_Unsafe_allocateMemory+0x109 (smunsafe.asm:685,
  0x013916F9 <OSB>jclscar_24+0x316f9<CSB>)
  java_lang_J9VMInternals_initializeImpl+0xad (internals.asm:813,
  0x0136745D <OSB>jclscar_24+0x745d<CSB>)
  java_lang_Class_forNameImpl+0x2c0 (jlcls_x.asm:350, 0x013740C0
  <OSB>jclscar_24+0x140c0<CSB>)
  java_lang_J9VMInternals_initializeImpl+0xad (internals.asm:813,
  0x0136745D <OSB>jclscar_24+0x745d<CSB>)
  resolveStaticMethodRefInto+0x209 (ressup.asm:2107, 0x003D56C9
  <OSB>j9vm24+0x356c9<CSB>)
  resolveStaticMethodRef+0x32 (ressup.asm:1896, 0x003D5472
  <OSB>j9vm24+0x35472<CSB>)
  resolveHelper+0x508 (javamisc.asm:1128, 0x003B0058
  <OSB>j9vm24+0x10058<CSB>)
  standardInit+0x1bb (stdinit.c:214, 0x013978EB
  <OSB>jclscar_24+0x378eb<CSB>)
  scarInit+0x8c (vm_scar.c:183, 0x0139A96C
  <OSB>jclscar_24+0x3a96c<CSB>)
  J9VMDllMain+0xa7 (vm_scar.c:220, 0x0139AFE7
  <OSB>jclscar_24+0x3afe7<CSB>)
  runJ9VMDllMain+0xcd (jvminit.c:2509, 0x003C6F0D
  <OSB>j9vm24+0x26f0d<CSB>)
  pool_do+0x54 (pool.c:451, 0x003E9274 <OSB>j9vm24+0x49274<CSB>)
  runInitializationStage+0x55 (jvminit.c:2471, 0x003CB1B5
  <OSB>j9vm24+0x2b1b5<CSB>)
  protectedInitializeJavaVM+0x575 (jvminit.c:6646, 0x003CE025
  <OSB>j9vm24+0x2e025<CSB>)
  j9sig_protect+0x41 (j9signal.c:144, 0x0036C241
  <OSB>J9PRT24+0xc241<CSB>)
  initializeJavaVM+0x168 (jvminit.c:1115, 0x003CE1E8
  <OSB>j9vm24+0x2e1e8<CSB>)
  JNI_CreateJavaVM+0x6e (jniinv.c:101, 0x003BA57E
  <OSB>j9vm24+0x1a57e<CSB>)
  JNI_CreateJavaVM+0xa3d (jvm.c:1602, 0x00346A0D
  <OSB>jvm+0x6a0d<CSB>)
  handleClose+0x1 (io_util_md.c:516, 0x00402E32
  <OSB>java+0x2e32<CSB>)
  canonicalize+0x2bf (canonicalize_md.c:275, 0x004098DE
  <OSB>java+0x98de<CSB>)
  BaseThreadInitThunk+0x12 (0x7619339A <OSB>kernel32+0x1339a<CSB>)
  RtlInitializeExceptionChain+0x63 (0x76F59EF2
  <OSB>ntdll+0x39ef2<CSB>)
  RtlInitializeExceptionChain+0x36 (0x76F59EC5
  <OSB>ntdll+0x39ec5<CSB>)
  .
  This issue only occurs when using the -Xtrace:trigger function
  "jstacktrace" on trace?point ranges that include j9jcl.62-66
  trace points (for
  example,?-Xtrace:trigger=tpnid{j9jcl.62-66,jstacktrace})
  

Local fix

• Don't use the -Xtrace:trigger option on the j9jcl.62-66
  tracepoints.
  

Problem summary

• The problem is caused when the -Xtrace:trigger option is used to
  request java stack traces for the j9jcl.62-66 tracepoints.
  

Problem conclusion

• This defect will be fixed in:
  6.0.0 SR11
  .
  The JVM has been updated to ensure that the stack can be walked
  when reporting the j9jcl.62-66 tracepoints.
  

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

  J9 COMMON CODE

• Fixed component ID

  620700127

Applicable component levels

• R600 PSY

     UP