search for: babeltrac

...idea (BCC rewriter should be a considerable solution). Let patch series 'Make eBPF programs output data to perf' be merged into upstream without the 'typeid' change. Before the decoding problem solved, we have to let user decode the BPF output themself manually or use perf script or babeltrace script. Thank you. ----------------- EXAMPLE ----------------- extern void output(int id, void *ptr, int size); #define OUTPUT_STR(name) \ struct name { #define OUTPUT_STR_END(name) \ }; \ unsigned long long __get_typeid_##name(struct name *) asm ("llvm.typeid.for....

...format, e.g. see http://diamon.org/ctf/) the default format for XRay traces would be useful? It seems it'd be nice to be able to reuse some of the tools that already exist for CTF, such as a graphical viewer (http://tracecompass.org/) or a converter library (http://man7.org/linux/man-pages/man1/babeltrace.1.html). LTTng already uses this format and linux perf can create traces in CTF format too. Probably it would be useful for at least some to be able to combine traces from XRay with traces from LTTng or linux perf? Maybe the current version of CTF may not have all the features that you need, but...

Hi llvm-dev, Recently, we've committed the beginnings of the llvm-xray [0] tool which allows for conveniently working with both XRay-instrumented libraries as well as XRay trace/log files. In the course of the review for the conversion tool [1] which turns a binary/raw XRay log file into YAML for human consumption purposes, a question arose as to how we intend to allow users to develop tools

On 2015/8/12 12:57, Alexei Starovoitov wrote: > On Wed, Aug 12, 2015 at 10:34:43AM +0800, Wangnan (F) via llvm-dev wrote: >> Think about a program like this: >> >> struct strA { int a; } >> struct strB { int b; } >> int func() { >> struct strA a; >> struct strB b; >> >> a.a = 1; >> b.b = 2; >>