IBM Support

PI15244: RDZ DEBUGGER GENERATES NULLPOINTEREXCEPTION AND THEN FAILS TO JUMP TO THE NEXT BREAKPOINT AFTER PRESSING F8

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Rational Developer for System z fails with NullPointerException
    when the RDz user is debugging a cics transaction multiple
    times. At some point, the debugger won't jump to the next
    breakpoint after pressing F8. The developer has to click on the
    active thread in the debug view and the debugger jumps to the
    breakpoint.
    At this time, variables won't be shown anymore in the variables
    view.
    
    The .log shows the following Exception every time:
    The NPE seems to be preceded by
    !ENTRY org.eclipse.jface 2 0 2014-02-04 13:35:51.346
    !MESSAGE Keybinding conflicts occurred.  They may interfere with
    normal accelerator operation.
    !SUBENTRY 1 org.eclipse.jface 2 0 2014-02-04 13:35:51.346
    !MESSAGE A conflict occurred for CTRL+SHIFT+M:
    Binding(CTRL+SHIFT+M,
    ParameterizedCommand(Command(com.ibm.debug.pdt.ui.monitorExpress
    ionAction,Ausdruck ᅦᆲberwachen,
      Dialog 'Ausdruck ᅦᆲberwachen' ᅦ￴ffnen,
    
    Category(org.eclipse.debug.ui.category.run,Ausfᅦᆲhren/Debug,Befe
    hlskategorie 'Ausfᅦᆲhren/Debug',true),
    
    ActionDelegateHandlerProxy(null,com.ibm.debug.pdt.internal.ui.ac
    tions.MonitorExpressionActionDelegate),
      ,,true),null),
    org.eclipse.ui.defaultAcceleratorConfiguration,
    com.ibm.debug.pdt.ui.debugging,,,system)
    Binding(CTRL+SHIFT+M,
    ParameterizedCommand(Command(c-s-m,c-s-m,
      ,
      Category(com.ibm.lpex.category.lpex,LPEX,LPEX,true),
    
    LegacyHandlerWrapper(ActionHandler(action=com.ibm.lpex.alef.Lpex
    KeyBindingAction@312085ca)),
      ,,true),null),
    org.eclipse.ui.defaultAcceleratorConfiguration,
    com.ibm.lpex.lpexScope,,,system)
    
    !ENTRY com.ibm.debug.pdt.core 4 0 2014-02-04 13:37:22.783
    !MESSAGE  [Reply processor] java.lang.NullPointerException
    !STACK 0
    java.lang.NullPointerException
    at
    com.ibm.debug.pdt.internal.core.model.ExpressionBase.fireChangeE
    vent(Unknown Source)
    at
    com.ibm.debug.pdt.internal.core.model.Expression2.update(Unknown
    Source)
    at
    com.ibm.debug.pdt.internal.core.model.EPDCReplyProcessor.process
    MonVarChg(Unknown Source)
    at
    com.ibm.debug.pdt.internal.core.model.EPDCReplyProcessor.process
    Reply(Unknown Source)
    at
    com.ibm.debug.pdt.internal.core.model.EPDCReplyProcessor.updateM
    odel(Unknown Source)
    at
    com.ibm.debug.pdt.internal.core.model.EPDCReplyProcessor.run(Unk
    nown Source)
    

Local fix

  • If the developer creates a new workspace or restarts RDz with
    the Eclipse option -clean, the debugger will work fine for a
    while until re-occurrence
    

Problem summary

  • RD/z throws a Null Pointer Exception while stepping through a
    program and monitoring variables. This causes debugging to fail
    and the workspace must be restarted in order to commence
    debugging again.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PI15244

  • Reported component name

    RATL DEV FOR SY

  • Reported component ID

    5724T0700

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-04-04

  • Closed date

    2015-02-04

  • Last modified date

    2015-05-19

  • 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

  • R851 PSY

       UP



Document information

More support for: Rational Developer for System z

Software version: 8.5

Reference #: PI15244

Modified date: 19 May 2015