Community
Participate
Working Groups
(1) Enter an exception breakpoint to catch "StackOverflowError" (2) Debug the following program. (3) The program stops, with a deep stack (slowly - which there is a bug for). (4) A bunch of errors appear in the log (attached). public class Overflow { public static void main(String[] args) { Overflow o = new Overflow(); o.recurse("a"); } public void recurse(String a) { recurse(a); } }
Created attachment 1240 [details] Log file
You may need to select various stack frames to make the errors occurr.
Cannot reproduce. Do you get this every time? Also, what VM are you running Eclipse on and what VM are you debugging the program with?
Happens on all VMs I tried, all the time - IBM1.3.0/1.3.1, Sun 1.2.2/1.3.1/1.4.1. You have to "run" in debug mode.
Sorry, on 1.4.1, I get a timeout exception and no stack frames appear. !ENTRY org.eclipse.debug.ui 4 120 Jun 05, 2002 09:00:06.910 !MESSAGE Error logged from Debug UI: !STACK 1 org.eclipse.debug.core.DebugException[5010]: org.eclipse.jdi.TimeoutException at org.eclipse.jdi.internal.connect.PacketReceiveManager.getReply (PacketReceiveManager.java:127) at org.eclipse.jdi.internal.connect.PacketReceiveManager.getReply (PacketReceiveManager.java:137) at org.eclipse.jdi.internal.MirrorImpl.requestVM(MirrorImpl.java:168) at org.eclipse.jdi.internal.MirrorImpl.requestVM(MirrorImpl.java:186) at org.eclipse.jdi.internal.ThreadReferenceImpl.frames (ThreadReferenceImpl.java:175) at org.eclipse.jdi.internal.ThreadReferenceImpl.frames (ThreadReferenceImpl.java:159) at org.eclipse.jdt.internal.debug.core.model.JDIThread.getUnderlyingFrames (JDIThread.java:483) at org.eclipse.jdt.internal.debug.core.model.JDIThread.createAllStackFrames (JDIThread.java:460) at org.eclipse.jdt.internal.debug.core.model.JDIThread.computeStackFrames (JDIThread.java:352) at org.eclipse.jdt.internal.debug.core.model.JDIThread.computeStackFrames (JDIThread.java:432) at org.eclipse.jdt.internal.debug.core.model.JDIThread.getStackFrames (JDIThread.java:336) at org.eclipse.debug.internal.ui.views.launch.LaunchViewEventHandler.doHandleSuspen dThreadEvent(LaunchViewEventHandler.java:195) at org.eclipse.debug.internal.ui.views.launch.LaunchViewEventHandler.doHandleSuspen dEvent(LaunchViewEventHandler.java:175) at org.eclipse.debug.internal.ui.views.launch.LaunchViewEventHandler.doHandleDebugE vents(LaunchViewEventHandler.java:95) at org.eclipse.debug.internal.ui.views.AbstractDebugEventHandler$1.run (AbstractDebugEventHandler.java:49) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages (Synchronizer.java(Compiled Code)) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages (Synchronizer.java(Compiled Code)) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java (Compiled Code)) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java (Compiled Code)) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java (Compiled Code)) at org.eclipse.ui.internal.Workbench.run(Workbench.java:1160) at org.eclipse.core.internal.boot.InternalBootLoader.run (InternalBootLoader.java:739) at org.eclipse.core.boot.BootLoader.run(BootLoader.java:462) at java.lang.reflect.Method.invoke(Native Method) at org.eclipse.core.launcher.Main.basicRun(Main.java:244) at org.eclipse.core.launcher.Main.run(Main.java:693) at org.eclipse.core.launcher.Main.main(Main.java:526) !ENTRY org.eclipse.jdt.debug 4 5010 Jun 05, 2002 09:00:07.00 !MESSAGE org.eclipse.jdi.TimeoutException occurred retrieving stack frames. !STACK 0 org.eclipse.jdi.TimeoutException at org.eclipse.jdi.internal.connect.PacketReceiveManager.getReply (PacketReceiveManager.java:127) at org.eclipse.jdi.internal.connect.PacketReceiveManager.getReply (PacketReceiveManager.java:137) at org.eclipse.jdi.internal.MirrorImpl.requestVM(MirrorImpl.java:168) at org.eclipse.jdi.internal.MirrorImpl.requestVM(MirrorImpl.java:186) at org.eclipse.jdi.internal.ThreadReferenceImpl.frames (ThreadReferenceImpl.java:175) at org.eclipse.jdi.internal.ThreadReferenceImpl.frames (ThreadReferenceImpl.java:159) at org.eclipse.jdt.internal.debug.core.model.JDIThread.getUnderlyingFrames (JDIThread.java:483) at org.eclipse.jdt.internal.debug.core.model.JDIThread.createAllStackFrames (JDIThread.java:460) at org.eclipse.jdt.internal.debug.core.model.JDIThread.computeStackFrames (JDIThread.java:352) at org.eclipse.jdt.internal.debug.core.model.JDIThread.computeStackFrames (JDIThread.java:432) at org.eclipse.jdt.internal.debug.core.model.JDIThread.getStackFrames (JDIThread.java:336) at org.eclipse.debug.internal.ui.views.launch.LaunchViewEventHandler.doHandleSuspen dThreadEvent(LaunchViewEventHandler.java:195) at org.eclipse.debug.internal.ui.views.launch.LaunchViewEventHandler.doHandleSuspen dEvent(LaunchViewEventHandler.java:175) at org.eclipse.debug.internal.ui.views.launch.LaunchViewEventHandler.doHandleDebugE vents(LaunchViewEventHandler.java:95) at org.eclipse.debug.internal.ui.views.AbstractDebugEventHandler$1.run (AbstractDebugEventHandler.java:49) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages (Synchronizer.java(Compiled Code)) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages (Synchronizer.java(Compiled Code)) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java (Compiled Code)) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java (Compiled Code)) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java (Compiled Code)) at org.eclipse.ui.internal.Workbench.run(Workbench.java:1160) at org.eclipse.core.internal.boot.InternalBootLoader.run (InternalBootLoader.java:739) at org.eclipse.core.boot.BootLoader.run(BootLoader.java:462) at java.lang.reflect.Method.invoke(Native Method) at org.eclipse.core.launcher.Main.basicRun(Main.java:244) at org.eclipse.core.launcher.Main.run(Main.java:693) at org.eclipse.core.launcher.Main.main(Main.java:526)
*** Bug 16491 has been marked as a duplicate of this bug. ***
Its unclear that we can do anything about this. It appears dependent on how well the VM can handle the stack overflow.
Do not itend to fix for 2.0
This is in the 2.1 readme notes. No further action planned.
Marking as "won't fix".
*** Bug 208533 has been marked as a duplicate of this bug. ***
It's been 4 years since anyone looked at this. Perhaps it is time for fresh look at it? Surely something has happened on the JVM side???
*** Bug 209607 has been marked as a duplicate of this bug. ***
*** Bug 258416 has been marked as a duplicate of this bug. ***
*** Bug 234798 has been marked as a duplicate of this bug. ***