Community
Participate
Working Groups
Build Identifier: 20100917-0705 "events lost" warnings (and possibly others) are not captured in the Problems view: they can only be seen from the terminal used to launch Eclipse. If Eclipse was launched from a menu entry or icon on the desktop or elsewhere, nothing will be seen. Reproducible: Always Steps to Reproduce: 1. Launch Eclipse from a terminal (e.g. "$ eclipse &") 2. Open the Linux Tools LTTng perspective 3. Bring the Problems view to the fore 4. Create an LTTng project 5. Import a trace with "events lost" problems (see attachment) 6. Create an experiment and add the trace to it 7. Open the experiment 8. Observe how the Problems view reports nothing at all while warnings scroll in the terminal window
Created attachment 186936 [details] Part 1 of a sample trace that will cause warnings to be issued when loaded into an LTTng perspective This trace generates hundreds of warnings like this: ** (Eclipse:14770): WARNING **: 594 events lost so far in tracefile /home/daniel/workspace/My LTTng Verification Project/Traces/trace6/vm_state_2 at block 2
Created attachment 186937 [details] Part 2 of a sample trace that will cause warnings to be issued when loaded into an LTTng perspective This trace generates hundreds of warnings like this: ** (Eclipse:14770): WARNING **: 594 events lost so far in tracefile /home/daniel/workspace/My LTTng Verification Project/Traces/trace6/vm_state_2 at block 2
These warnings are from liblttvtraceread, the C library that parses the traces. The lib writes directly to stderr and does not provide any notification mechanism that can be used by the viewer through the JNI wrapper. There's not much that we can do on this front without the help of the lib guys. Monitoring and parsing the console output is not worth it, IMHO. This is where things get interesting. LTTng is moving towards the Common Trace Format (CTF), a new, more generic binary trace format. They will adapt their format along this standard. We are also told that there will be a utility to convert the old trace formats to the new one. The good news is that we are working on an Eclipse implementation of a CTF parser - in Java - that will be used in lieu of the current, legacy, C libs. The bad news is that we won't fix this particular problem. Unless someone is interested in providing a fix for this issue, I will close it shortly.
Legacy LTTng support is being removed in Linux Tools 2.0.
