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

Bug 362123

Summary:	Step into / step over / step return gets disabled and do not do anything
Product:	[Eclipse Project] Platform	Reporter:	Oleg Besedin <ob1.eclipse>
Component:	Debug	Assignee:	Platform-Debug-Inbox <platform-debug-inbox>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	P3	CC:	pawel.1.piech, remy.suen
Version:	3.8
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Oleg Besedin

2011-10-26 14:17:33 EDT

- Installed Eclipse SDK I20111025-1800
- Create a clean workspace
- Create a plug-in project, I used:
 New -> Project -> Plug-In project -> "Hello, World"
- Place a break point in SampleAction#run() on the "MessageDialog.openInformation()" line
- Debug Eclipse application

- Trigger breakpoint by selecting Sample Menu -> Sample Action
- Press "Step Over" on the toolbar or press F6 
- Nothing happens

Same for "step into", "step return".

I see the same behavior on Mac and Windows 7, both 64 bit.

For a breakpoint placed in another spot (such as SampleAction.init()) stepping works fine.

Comment 1 Pawel Piech

2011-10-26 16:34:04 EDT

Unless I'm missing something, the described behavior is correct.  User is stepping over an operation that opens a modal dialog.  So while the dialog is open the step operation is "running".  When I try to reproduce, I see the state of the thread correctly changing to running (with running icon overlay), and at this point the run actions become disabled.  

The only fault I can find is that stack frames are also supposed to get the green triangle overlay.  At least that's what happens in CDT, I'm not sure if JDT supported this feature.

Please reopen if I made a mistake.

Comment 2 Oleg Besedin

2011-10-27 09:38:33 EDT

You are correct. I checked and it works the same way in 3.7.

The absence of UI indicators saying that the thread is running does look like a bug to me, but apparently it was this way before, so I'll leave it up to you to decide if this should be a bug or not.