TCF Debugger: Fixed: step out command fails with NullPointerException if stack trace is not available

1 files changed, 2 insertions, 1 deletions

diff --git a/plugins/org.eclipse.tm.tcf.debug/src/org/eclipse/tm/internal/tcf/debug/actions/TCFActionStepOut.java b/plugins/org.eclipse.tm.tcf.debug/src/org/eclipse/tm/internal/tcf/debug/actions/TCFActionStepOut.java
index 1b0e3b935..31d5dec8e 100644
--- a/plugins/org.eclipse.tm.tcf.debug/src/org/eclipse/tm/internal/tcf/debug/actions/TCFActionStepOut.java
+++ b/plugins/org.eclipse.tm.tcf.debug/src/org/eclipse/tm/internal/tcf/debug/actions/TCFActionStepOut.java
@@ -92,7 +92,8 @@ public abstract class TCFActionStepOut extends TCFAction implements IRunControl.
             if (bp == null) {
                 TCFDataCache<IStackTrace.StackTraceContext> frame = getStackFrame();
                 if (!frame.validate(this)) return;
-                Number addr = frame.getData().getReturnAddress();
+                Number addr = null;
+                if (frame.getData() != null) addr = frame.getData().getReturnAddress();
                 if (addr == null) {
                     exit(new Exception("Unknown stack frame return address"));
                     return;