Bug 33136 - Wrong editor when hitting breakpoint during scrapbook execution
Summary: Wrong editor when hitting breakpoint during scrapbook execution
Status: RESOLVED INVALID
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.1   Edit
Hardware: All All
: P3 normal with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
: 32761 (view as bug list)
Depends on:
Blocks:
 
Reported: 2003-02-25 16:33 EST by Joe Szurszewski CLA
Modified: 2009-08-30 02:10 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Joe Szurszewski CLA 2003-02-25 16:33:56 EST
In a scrapbook page, enter code like:


Square square = new Square();


return square.square(3);




This assume a class 'Square' with a method:


public int square(int i) {


  return i*i;


}




Set a breakpoint in the square() method, then select the code in the scrapbook 
and hit Display.  The breakpoint is hit, but the debugger tries to show the 
source in the scrapbook page, not the editor for Square.
Comment 1 Darin Wright CLA 2003-02-26 16:34:51 EST
If I re-select the top stack frame, source is shown.
Comment 2 Darin Wright CLA 2003-03-03 10:32:09 EST
*** Bug 32761 has been marked as a duplicate of this bug. ***
Comment 3 Darin Wright CLA 2003-03-03 10:35:55 EST
This appears to be a workbench bug. The problem only occurrs when the 
perspective is being switched. For example, from the java perspective to the 
debug perspective. This can be seen by following the scrapbook example below. A 
simpler test case is:

* Debug to a breakpoint
* switch to the java perspective
* Close the editor that the breakpoint is in
* open another (different) editor
* switch to the debug perspective

-> The debugger opens the editor in which the breakpoint is, but the workbench 
brings the "oldActivePart" to the top, covering up the editor that the debugger 
brought to the top.

-> This can be seen by placing a breakpoint in WorkbenchPage#bringToTop
(IWorkbenchPart)
Comment 4 Nick Edgar CLA 2003-03-11 15:37:29 EST
Defer
Comment 5 Darin Wright CLA 2003-03-11 15:44:59 EST
This actually effects more than the scrapbook. For example:

* in the Java perspective, open an editor on some compilation unit (for 
example "DebugPlugin".
* create a launch configuration for "junit.samples.VectorTest" that does not 
switch perspectives when launching (via common tab)
* place a breakpoint in VectorTests
* close the VectorTests editor
* debug VectorTests
* when the breakpoint is hit, the debug perspective is activated, but the 
associated source is not shown -> instead "DebugPlugin" is shown

Thus, this means that if a user switches away from the debug perspective, and 
then a breakpoint is hit, the proper source may not be shown.
Comment 6 Tod Creasey CLA 2006-06-26 09:11:59 EDT
Is this still an issue in 3.2?
Comment 7 Denis Roy CLA 2009-08-30 02:10:35 EDT
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.