Community
Participate
Working Groups
I am a performance analyst for an adopting product. We perform many automated runs of the product. It would be very useful for us to be able to capture anything written to the console into the .log file for later browsing. The current eclipse.exe option -consoleLog, according to http://www.eclipse.org/eclipse/platform-core/documents/3.1/debug.html means that "anything you log to the log file should be logged to the console as well" I would like to request an option that means "anything you log to the console should be logged to the log file as well" This would allow us to catch any accidental System.out and System.err prints (or easily include them for debugging purposes). The only way to currently do this is to launch eclipse as a pure java command, trying to get all the parameters correct for the product, which is not desirable. The option could be -logConsole, or something else.
This can be done with any shell. On Windows try this: eclipsec -debug >>output.txt You will see the output added to the given file.
While I can get this working (thank you!), it is less than optimal, especially for adopting products (we have a separate executable, so I'd have to bypass that and launch eclipsec directly, which I'd rather not do since I want to launch the same way as a customer would). It really would be convenient to have it all in the .log file. Anyway, it's an enhancement request. Your decision obviously.
One thing I can't get working that is critical for me is to retain the ability to do a Ctrl-Break and force a javacore dump (in the rare case of infinite loops or deadlocks). So, I'm back to relying on this enhancement request.
Ctrl+Break works for me when running with eclipsec.exe. If you're running eclipsec.exe from a command prompt window, just give that window focus and hit Ctrl+Break.
This only works if java.exe is used instead of javaw.exe. Even so, I cannot figure out how to launch such that: (1) console output (stdout & stderr) are captured to a file (2) retain use of the command prompt that launched eclipsec (3) be able to capture javacore dumps by use of Ctrl-Break I have tried just eclipsec ... >> console.log 2>&1 which gives me 1 and 3. I have tried putting eclipsec .... >> console.log 2>&1 into a bat file so that I can use the start command (thus getting 1 and 2), but then I can't get 3--Ctrl-Break just quits the bat file. I have tried using start eclipsec ... >> console.log 2>&1 which gives me 2 and 3, but the shell doesn't know that I want the output of the eclipsec command instead of the start command. So I can get any 2 of the requirements but not all three (without the enhancement requested in this bug). Please prove me wrong if possible. :-)
Correct, you only get 1) and 3) with eclipsec.exe.
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. If you have further information on the current state of the bug, please add it. 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.
