IBM Support

IV38930: SEGMENTATION ERROR

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Error Message: Seg fault from JIT compilation thread.
    .
    Stack Trace: monitor_enter_three_tier+0x28e (j9thread.c:3323,
    0x7ED7361E <OSB>J9THR26+0x361e<CSB>)
    jvmtiHookCheckForDataBreakpoint+0x9d (jvmtihook.c:2592,
    0x7EE31FDD <OSB>j9jvmti26+0x11fdd<CSB>)
    J9HookDispatch+0x88 (hookable.c:176, 0x7F3B10B8
    <OSB>J9HOOKABLE26+0x10b8<CSB>)
    jitCTResolveInstanceFieldRef+0x91 (ctsupport.c:332, 0x7F255F31
    <OSB>j9jit26+0x365f31<CSB>)
    TR_ResolvedJ9Method::fieldAttributes+0x78 (j9method.cpp:6318,
    0x7EF16E68 <OSB>j9jit26+0x26e68<CSB>)
    TR_SymbolReferenceTable::findOrCreateShadowSymbol+0x60
    (symreftab.cpp:2195, 0x7EF9E570 <OSB>j9jit26+0xae570<CSB>)
    TR_ByteCodeIlGenerator::loadInstance+0x1c (walker.cpp:6342,
    0x7F241ECC <OSB>j9jit26+0x351ecc<CSB>)
    TR_ByteCodeIlGenerator::walker+0x20bb (walker.cpp:462,
    0x7F24B7EB <OSB>j9jit26+0x35b7eb<CSB>)
    TR_ByteCodeIlGenerator::genILFromByteCodes+0x21f
    (ilgenerator.cpp:542, 0x7F23C53F <OSB>j9jit26+0x34c53f<CSB>)
    TR_ByteCodeIlGenerator::genIL+0x1f (ilgenerator.cpp:104,
    0x7F23D3FF <OSB>j9jit26+0x34d3ff<CSB>)
    TR_ResolvedMethodSymbol::genIL+0x1ab (symbol.cpp:779, 0x7EF9119B
    <OSB>j9jit26+0xa119b<CSB>)
    TR_Compilation::compile+0x8fa (compilation.cpp:1337, 0x7EF5BBCA
    <OSB>j9jit26+0x6bbca<CSB>)
    TR_CompilationInfoPerThreadBase::compile+0x4ce
    (compilationthread.cpp:6695, 0x7EEFA72E
    <OSB>j9jit26+0xa72e<CSB>)
    TR_CompilationInfoPerThreadBase::wrappedCompile+0xadb
    (compilationthread.cpp:6441, 0x7EEFE8CB
    <OSB>j9jit26+0xe8cb<CSB>)
    j9sig_protect+0x44 (j9signal.c:150, 0x7EDFF0E4
    <OSB>J9PRT26+0xf0e4<CSB>)
    TR_CompilationInfoPerThreadBase::compile+0x588
    (compilationthread.cpp:5733, 0x7EEFF128
    <OSB>j9jit26+0xf128<CSB>)
    protectedCompilationThreadProc+0x44e
    (compilationthread.cpp:3058, 0x7EEFFA9E
    <OSB>j9jit26+0xfa9e<CSB>)
    j9sig_protect+0x44 (j9signal.c:150, 0x7EDFF0E4
    <OSB>J9PRT26+0xf0e4<CSB>)
    compilationThreadProc+0x230 (compilationthread.cpp:2695,
    0x7EF00380 <OSB>j9jit26+0x10380<CSB>)
    thread_wrapper+0xda (j9thread.c:1153, 0x7ED7464A
    <OSB>J9THR26+0x464a<CSB>)
    _endthread+0x48 (0x78AFC55C <OSB>msvcr100+0x5c55c<CSB>)
    _endthread+0xe8 (0x78AFC5FC <OSB>msvcr100+0x5c5fc<CSB>)
    GetModuleFileNameA+0x1ba (0x7C80B729 <OSB>kernel32+0xb729<CSB>)
    .
    

Local fix

  • N/A
    

Problem summary

  • The crash originated from accessing an already destroyed mutex
    within an already disposed jvmti environment.
    

Problem conclusion

  • This defect will be fixed in:
    7.0.0 SR5
    6.0.1 SR6
    6.0.0 SR14
    .
    All jvmti environment iterators should skip processing of any
    jvmti environment that has been marked as disposed.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV38930

  • Reported component name

    J9 COMMON CODE

  • Reported component ID

    620700127

  • Reported release

    260

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-03-28

  • Closed date

    2013-04-11

  • Last modified date

    2013-04-11

  • 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

  • R260 PSY

       UP

  • R600 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSNVBF","label":"Runtimes for Java Technology"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
21 February 2022