Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 180119 - Focus lost in debug view
Summary: Focus lost in debug view
Status: RESOLVED DUPLICATE of bug 177910
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-29 23:29 EDT by Olivier Thomann CLA
Modified: 2007-03-30 11:10 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Olivier Thomann CLA 2007-03-29 23:29:45 EDT
Using I20070323-1616, sometimes while debugging the debug view is losing the focus on the suspended thread.
I need to click again the current suspended thread to get back the contents of the Variable view or evaluate an expression.
Comment 1 Darin Wright CLA 2007-03-30 10:11:47 EDT
Olivier, is this a dup of bug 177910 ?
Comment 2 Olivier Thomann CLA 2007-03-30 10:18:50 EDT
Not sure.
My problem is about the fact that the suspended frame sometimes is losing the selection and it has to be reselected in order to continue to debug (step over, step into, inpect code,...).
If you believe this is a dup, close it as a dup.
Comment 3 Darin Wright CLA 2007-03-30 10:37:20 EDT
If the thread is still expanded, this does not sound like a dup. Please attach a screen shot the next time this happens.
Comment 4 Olivier Thomann CLA 2007-03-30 10:43:49 EDT
No, it is not expanded anymore.
It is collapsed on the suspended frame. I need to expand it again and then reselect the first frame.
So it might be a dup.
Comment 5 Michael Rennie CLA 2007-03-30 11:08:29 EDT
I am starting to see Olivier's problem as well using  I20070327-0800
on WinXP
Comment 6 Darin Wright CLA 2007-03-30 11:10:19 EDT
Yes, this is a dup - turn off system thread filters in the debug view as a workaround.

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