Community
Participate
Working Groups
Running or debugging any compiled application that writes to standard output or standard error with long lines (exceeding the console width, for example several kilobytes) generates incorrect display where the long line appears below the effective point where it should be. In addition, if the console is set to a fixed width, we see a series of OutOfBoundException (internal error), displayed in an alert box of Eclipse with the summary "Reveal End of Document". The detail about all these multiple errors (there may be thousands if the application generates lots of output) does not include a complete stacktrace, but just the following: An internal error has occurred. java.lang.ArrayIndexOutOfBoundsException In most cases, this is not blocking, but sometimes it can can Eclipse to reach out of memory conditions due to the accumulated errors, making it unusable and crashing it. -- Configuration Details -- Product: Eclipse Platform 3.6.0.v201006080911 (org.eclipse.platform.ide) Installed Features: org.eclipse.platform 3.6.0.v20100602-9gF78GpqFt6trOGhL60z0oEx3fz-JKNwxPY
debug owns the console view.
I forgot to check the Eclipse log file, so this bug is exactly the same as Bug 243877.
I forgot to check the Eclipse log file, so this bug is exactly the same as Bug 243877. But not that this is not restricted to Fixed width mode of the console. There's still a problem of refresh in the non-fixed width mode, where the text is displayed at the wrong position, and then duplicated at the right position when the program terminates. Any program that just writes a single long line (for example in a loop of System.out.print(someInteger+", "), finally terminated by System.out.println() will have this problem. Such program is quite common when running a static main function integrated in some class to test, where the internal class data or detailed processing info is just dumped to the standard output.
Thanks for reporting back Philippe, I will mark this as a dupe of bug 243877, and add you steps to reproduce to that bug. *** This bug has been marked as a duplicate of bug 243877 ***