Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 102646

Summary: Debugger useless when getting a StackOverflowError
Product: [Eclipse Project] JDT Reporter: Peter Larsen <peblpebl>
Component: DebugAssignee: JDT-Debug-Inbox <jdt-debug-inbox>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: P3    
Version: 3.1   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description Peter Larsen CLA 2005-07-04 09:28:15 EDT 
When debugging a program that throws an StackOverflowError, the debug window
shows the thread as "not responding" after hanging for a while, and thats it. I
cannot view the the stack or see that the reason execption (stackOverflow). 

I would like to atleast know that it is a stackOverflow (and therefor the stack
  might not be available). Secondly, I would like to have access to ca. 4 last
calls with parameter, which usually is enough for deducing why the code calls
itself recursively.

A "workaround" is to run without debuging, and in the console output conclude
that it is a StackOverflow that the debugger catches.

Eclipse 3.1 final.
Comment 1 Darin Wright CLA 2005-07-05 10:18:21 EDT 

*** This bug has been marked as a duplicate of 41392 ***