Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 286577

Summary: [display] Running "Display" in Display View writes result to Display View, but also to Console View, even if no print statements were executed
Product: [Eclipse Project] JDT Reporter: David M. Karr <davidmichaelkarr>
Component: DebugAssignee: JDT-Debug-Inbox <jdt-debug-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: minor    
Priority: P3 CC: pawel.1.piech
Version: 3.5   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: stalebug
Attachments:
Description Flags
Java source file for test case none

Description David M. Karr CLA 2009-08-13 16:56:48 EDT
Created attachment 144474 [details]
Java source file for test case

Build ID: 20090621-0832

Steps To Reproduce:
1. Set up project with attached test case.
2. Set breakpoint in "go" method.
3. Run test.
4. At breakpoint, step to first statement inside loop, with "foo" in scope.
5. Bring up Display View.
6. Enter "foo.marker" in Display View.
7. Select "foo.marker" in Display View and press Ctrl-Shift-d for the "Display" function.
8. You'll see the "Console View" suddenly appear, with a new line of "abc" appearing in the view.
9. If you go back to the "Display View", you'll see the correct "(java.lang.String) abc" appearing on the line after "foo.marker".


More information:
I know why the Console View gets the focus, it's because something is displayed to the console, and my preferences say to make the Console View visible when there is new content.  The problem is not that the Console View becomes visible, the problem is that what I did shouldn't have written content to the Console.  As the content I wanted went to the Display View, that's all that it should do. There's no reason to write the content to the Console View.
Comment 1 Eclipse Genie CLA 2020-01-28 06:47:14 EST
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.