Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 169968 - Variable names in variables view missing
Summary: Variable names in variables view missing
Status: RESOLVED DUPLICATE of bug 173898
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-01-09 09:04 EST by Benno Baumgartner CLA
Modified: 2007-04-23 12:14 EDT (History)
1 user (show)

See Also:


Attachments
screen shot (130.05 KB, image/png)
2007-01-09 09:05 EST, Benno Baumgartner CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Benno Baumgartner CLA 2007-01-09 09:04:29 EST
I20061219-1300

1. Create a new Java Project 'JUnit'
2. Import 'junit3.8.1src.zip'
3. Set a breakpoint on first line of 'junit.samples.VectorTest.setUp()'
4. Debug 'VectorTest' as 'Java Application'
5. When the breakpoint is hit step after creation of 'fFull'
6. Expand 'fFull' in the variable view
7. 'Resume'
Is: 
 Variable view shows tree without variable names (see screen shot)
Comment 1 Benno Baumgartner CLA 2007-01-09 09:05:56 EST
Created attachment 56626 [details]
screen shot
Comment 2 Darin Wright CLA 2007-01-16 09:32:21 EST
Does this happen every time? I have not been able to reproduce.
Comment 3 Benno Baumgartner CLA 2007-01-16 10:42:55 EST
No, not every time, but very often (maybe 95%). And not all names are missing all the time. It seams, that the tree is not redrawn when the breakpoint is hit (the tree shows part of the old content). Pressing 'Step Over' after the breakpoint is hit does redraw the tree. This is in I20070109-1805
Comment 4 Darin Wright CLA 2007-04-23 12:14:49 EDT
We've made many fixes around this lately. Cannot reproduce  - marking as dup of related bug 173898.

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