IBM Support

PI41911: DBX COMMAND RESULTS IN NULLPOINTEREXCEPTION WHEN DEBUGGING C++ PROGRAM USING RDZ V9.1.1.1

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • dbx command results in NullPointerException when debugging C++
    program using Rational Developer for System z v9.1.1.1
    
    !ENTRY org.eclipse.core.jobs 4 2 2015-05-19 16:53:45.813
    !MESSAGE An internal error occurred during: "Debug Source
    Lookup".
    !STACK 0
    java.lang.NullPointerException
        at
    com.ibm.debug.pdt.internal.ui.PDTModelPresentation.getDefaultEdi
    torID(Unknown Source)
        at
    com.ibm.debug.pdt.internal.ui.PDTModelPresentation.useDefaultEdi
    tor(Unknown Source)
        at
    com.ibm.debug.pdt.internal.ui.PDTModelPresentation.getEditorInpu
    t(Unknown Source)
        at
    org.eclipse.debug.internal.ui.LazyModelPresentation.getEditorInp
    ut(Unknown Source)
        at
    org.eclipse.debug.internal.ui.sourcelookup.SourceLookupFacility.
    lookup(Unknown Source)
        at org.eclipse.debug.ui.DebugUITools.lookupSource(Unknown
    Source)
        at
    org.eclipse.debug.internal.ui.elements.adapters.StackFrameSource
    DisplayAdapter$SourceLookupJob.run(Unknown Source)
        at org.eclipse.core.internal.jobs.Worker.run(Unknown Source)
    
    The problem is reproducible with the following commands for
    example:
    
    cxx -c
    -Wc,"XPLINK,DEBUG(FORMAT(DWARF),SYMBOL),LANGLVL(EXTENDED),FLAG(W
    ),LP64,WARN64" tstHello.C
    cxx -Wl,xplink,lp64 -o tstHello tstHello.o
    dbgld tstHello
    dbx -p 9.142.33.52:8001 ./tstHello
    Observe NPE error and see stack in <workspace>\.metadata\.log
    
    There is no NullPointerException with the following commands:
    xlc -g -o tstHello tstHello.C
    dbx -p 9.142.33.52:8001 ./tstHello
    

Local fix

  • Set "Always use Debugger Editor while debugging" checkbox in:
    Menu
    >> Window
       >> Preferences
          >> Run / Debug
             >> Compiled Debug
                >> Debug Editors
    

Problem summary

  • If a debug engine fails to provide a non zero language ID during
    a debug session the UI would throw a null pointer exception and
    the editor would fail to open.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PI41911

  • Reported component name

    RATL DEV FOR SY

  • Reported component ID

    5724T0700

  • Reported release

    911

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-05-28

  • Closed date

    2015-10-16

  • Last modified date

    2015-10-16

  • 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

    RATL DEV FOR SY

  • Fixed component ID

    5724T0700

Applicable component levels

  • R911 PSY

       UP



Document information

More support for: Rational Developer for System z

Software version: 9.1.1

Reference #: PI41911

Modified date: 16 October 2015