| Summary: | NPE switching to debug perspective | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | John Arthorne <john.arthorne> | ||||
| Component: | UI | Assignee: | Stefan Xenos <sxenos> | ||||
| Status: | RESOLVED DUPLICATE | QA Contact: | |||||
| Severity: | major | ||||||
| Priority: | P1 | CC: | csmclaren, douglas.pollock, eclipse, michaelvanmeekeren, sxenos, Tod_Creasey | ||||
| Version: | 3.0 | ||||||
| Target Milestone: | 3.0 M9 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 2000 | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
John Arthorne
Created attachment 8882 [details]
JPG of broken debug perspective
This resulted in a broken debug perspective with a large grey area at the
bottom. See screen shot.
If I had to guess I'd say this is due to the breakage in either 15822 or 50618 introduced by the presentation work. I am unable to reproduce this problem...can you reproduce it consistantly? Are you running in a clean workspace? Are you launching a test plugin or plugins from an eclipse CVS module? I added the following to 54928: This could be some kind of timing issue... where you're trying to open the view in a perspective that hasn't gotten itself into a working state... it could be that you'll need to wrap your logic in LaunchView.showViewsForCurrentSelection in a WorkbenchJob to ensure that the perspective is in a happy state. I get this one everytime I try and step through to another class with the debugger. It is failing on opening the editor in the debug perspective. This should be P1 - the debugger is unusable with it. STEPS 1) Set a breakpoint 2) Run the run time workbench 3) When the breakpoint is hit step through until you hit a point where a new editor needs to open. I'm unable to reproduce this. (Running the code in HEAD, 20040412). I've tried the original steps in this report, and Tod's steps in comment 7, but neither of them throw the exception. I was never able to reproduce with my original steps. At the time we surmised it was a timing issue. does the code look like it would properly protect itself from an NPE or that NPEs would be possible in certain scenarios? If not then I suggest we close this. *** This bug has been marked as a duplicate of 54928 *** |