My problem is unable to list and view TRACEPOINTs in application part using
trace.py.
Command: ./scripts/run.py --trace=hello
Get Trace: scripts/trace.py extract && scripts/trace.py list (nothing shows
up, it uses GDB to extract tracepoints)
I think it is due to there are no tracepoint_patch_si
I have to admit it's been a long while (a few years) since I looked deeply
into our tracepoint implementation, so I'm quite rusty.
I thought that in the past OSv tracepoints *did* work in modules - a good
example is the test tests/tst-tracepoint - but I'm not sure this test
actually tests everythin
This is my example code.
#include
#include
TRACEPOINT(trace_hello, "i=%d", int);
int main(){
printf("Hello from C code\n");
printf("enabled: %lx\n", trace_hello.enabled());
for(int i =0; i<128;++i){
trace_hello(i);
}
return 0;
}
It seems that TRACEPOINT use tracepoint_patch_sites sections wh
I think it should be possible given this file which is part of java app has
tracepoints -
modules/java-base/balloon/jvm_balloon.cc.
But I have not tested it myself.
Can you give us your example?
Waldek
On Monday, August 31, 2020 at 10:33:27 AM UTC-4 Wonsup Yoon wrote:
> Hi,
>
> Is it pos
