Bugzilla – Full Text Bug Listing
| Summary: | Main thread not shown when threads groups are turned on. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Pawel Piech <pawel.1.piech> | ||||
| Component: | Debug | Assignee: | JDT-Debug-Inbox <jdt-debug-inbox> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | Michael_Rennie | ||||
| Version: | 3.5 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Whiteboard: | stalebug | ||||||
| Attachments: |
|
||||||
Do you think this is a dupe of bug 126379? It sounds like we are just failing to update the thread group item properly. Do you recall if double-clicking the target (forcing the children to update) caused the group to refresh properly? (In reply to comment #1) > Do you think this is a dupe of bug 126379? It sounds like we are just failing > to update the thread group item properly. Do you recall if double-clicking the > target (forcing the children to update) caused the group to refresh properly? I didn't even know that double-clicking an item forced a refresh. But I don't think it's the same as 126379. In fact 126379 is technically fixed because we changed default implementation of model selection policy to select the parent element if a currently selected element is removed from tree. This bug to me seemed to be caused by conflicting data being returned by the model. But I didn't try to debug it at the time (or more recently). This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. |
Created attachment 134679 [details] Screenshot of Debug view with missing thread. I ran the LoopForever test program and I stepped over the end of the main function so that I was steping through the Thread.exit() method. I switched back thread groups on and off a few times, as well as Show System Threads. Then I stepped a few times and did the same. Eventually I ended up with what's in the attached screenshot.