Target core-image-sato-sdk uses lttng-2.0, but in eclipse we use lttng, so in this test circle the cases about lttng are blocked. Branch:poky/1.2_M3 CommitId: 320558f494c618f53e0c773db3ea0109476e8359
Since lttng-2.0-ust is quite different in term of usage scenario, we need to investigate how much effort we need to modify our plugin to support lttng-2.0-ust. Or we should use lttng instead of lttng-2.0 in our sdk images.
After change the PREFERRED_VERSION_lttng-ust to "0.16", we can get the lttng-ust output data. But when opening the trace, the eclipse lttng plugin only support kernel trace type, so I can't open that user mode trace.
In lttng there's only kernel type, this is known issue. I've checked with upstream and there's no intention to fix it since a new lttng for 2.0 is under development. But since kernel type and user type the output is the same select kernel type will open the trace output in the viewer. Let me know if this won't. Also, I'm assuming this means the 0.16 still works with the new kernel. If so, please mark the bug fixed.
A yocto patch has been sent out for merge to use lttng-ust instead of lttng2-ust in the target system. http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=llu/bug2062&id=50f58e5b24baf92b358cd08e6175fd8621ebc34e
change the name of lttng-ust of 2.x to lttng2-ust, so both lttng-ust of 2.x and 1.x can coexist. Fixed at http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=fb7eeb395402ce6ec923cd4be411de2ddbe61310
Fixed and Verified on Milestone 1.2M4-rc1. tree/branch: poky/1.2_M4 commitID:4d9f4d6ac25f39fe6d5491d05c7a26195bab648b