Community
Participate
Working Groups
Currently the error stream is sent straight to the console. Since message boxes are already used to display errors and how to fix them, there should be no need for the same console output. It would be nice if the error stream of stap was sent to a file, so there would be no need to create an error stream listener just to grab that data.
Callgraph currently prints the first 500 lines of error to TEMP_ERROR_OUTPUT which is by default PluginConstants.getDefaultOutput() + "stapTempError.error" for debugging purposes. There should be a listener registered somewhere on the process that updates the Console for error output, if we could find it we could probably deregister it.
Yes this is true. TEMP_ERROR_OUTPUT contains the data collected from the error stream. However, the data is collected by using a listener on the error stream. The error stream itself outputs to the console. By redirecting the error stream to a file we could (maybe) eliminate the need to have that listener, and at the same time eliminate the output to console.
(In reply to comment #2) > Yes this is true. TEMP_ERROR_OUTPUT contains the data collected from the error > stream. However, the data is collected by using a listener on the error stream. > The error stream itself outputs to the console. By redirecting the error stream > to a file we could (maybe) eliminate the need to have that listener, and at the > same time eliminate the output to console. You're right, so avenues of attack: - Redirect error from command to /dev/null (may interfere with error collection) - Attempt to disengage the listener that is writing errors to the console - Attempt to modify the listener to output to a file instead of to console The middle two are the more attractive options. Is removing console error output what we really want to do? We can circumvent most of the problems by doing additional checks before running stap, which would leave just the parsing/compile-time errors in the console log. It could be useful for users to see those errors as they are presented by SystemTap
The console _in_ Eclipse can have error messages. We just don't want any going to the terminal from which Eclipse was launched (stderr).
When severin said : "I get: /tmp/org.eclipse.linuxtools.profiling.launch12756903992658802859707393390776.sh: line 2: exec: stap: not found on the console and an error dialog pops up that SystemTap is not installed. I think this is expected behaviour." he was refering to the eclipse console. I'm pretty sure we don't have any output being sent to the console from which eclipse is launched. The discussion charley and I were having pertained specifically to avoiding outputting to the eclipse console, but since this is acceptable I guess we can close this bug?
Yes, feel free to resolve. I was confused by the overloaded word "console" :)
Won't fix the "outputting to eclipse console" since this is valid, and text being sent to the console from which eclipse was launched is not a an issue.
