| Summary: | Normal console sometimes gets accidentally replaced by an empty stack trace console | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Stefan Matthias Aust <sma> |
| Component: | Debug | Assignee: | Platform-Debug-Inbox <platform-debug-inbox> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | chance.yohman, eclipse, fillg1 |
| Version: | 3.1 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Stefan Matthias Aust
Consoles are removed when you remove the associated launch. If you have not removed the launch, the console is still accessible from the console view. There is a drop down action in the toolbar that allows you to choose from available consoles. Otherwise, simple select the associated launch in the debug view to see the associated console. Sorry, I wasn't clear enough: I do not remove the launcher and the console view is still there, but after the program printed something and terminated, that "<terminated> console" sub-view is replaced by an empty "Java Stack traces" sub-view for no obvious reason. Unfortunately, I cannot reproduce the problem... it happens only sometimes. And if I re-run the application, the "<terminated> console" stays. However, I know that other people on the German Hava news group already reported the same problem. I'll ask them to comment on this problem, too. I have this problem too, with 3.1 RC2: After running an program, the console-view sometimes becomes cleaned, so tat the output is no longer visible. Does this happen on JDK 1.4.X or 1.5? I was using JDK 1.6.0-b40. It should have been 1.5. I now have installed RC3 and couldn't reproduce the problem til now. Do you have the "Pin Console" button turned on? I'm still not clear on this. Have you ever seen the behavior you describe when using 1.4 or 1.5? I do not have a 1.6 vm to test on and I have not been able to reproduce this bug on any vm that I have access to. I'm now running Eclipse on 1.5.0_03 and I think, I can reproduce the issue. 0. Create a Java project. 1. Create a new class with a simple "Hello, World" Java application. 2. Create and run new launch configuration (editor's context menu: Run As | Java Application) 3. Run it (should open a console view if not already open and show "Hello, World"; so far so good) 4. Now edit the class (inserting a single space should do the trick) but do NOT save it. 5. Press Ctrl+F11 to run the application again. 6. A "Save Resources" dialog is poping up, the source file is selected, press RETURN. 7. The application runs, something is displayed BUT the sub view is immediately removed, only displaying "A console is not available." Seems to happen on 1.4.2 and 1.5 when the General preference to "Always run in background" is "off". When on, I do not see the behavior. An interesting bug, bug none-the-less, deferred for post 3.1 consideration. *** Bug 101222 has been marked as a duplicate of this bug. *** I am unable to reproduce this on I20050624-1300 (ooops, I can reproduce in a fresh workspace). I downloaded that build and I can still reproduce the issue. The console vanishes if you run an application with modified source via Ctrl+F11. (In reply to comment #14) I have this problem, too. The console tab is displayed but I get a message that the no console is available. I closed the console tab and chose Run > Java application again - and then it worked. I am content with this work-around for now. *** Bug 112273 has been marked as a duplicate of this bug. *** I am running eclipse 3.1.1 on Mac OS X 10.3.9 with java sdk 1.4.2. Same problem - before running a program, the title bar of the console shows "no console available" after running, it changes to <terminated> blah blah...but the system.out.println output is not shown. This happens every time I use eclipse. satguru's workaround doesn't work for me. Fixed in 3.2 *** This bug has been marked as a duplicate of 128452 *** |