Btrace provides annotations to allow users to specify probes and actions easily.
For example, with the annotation, we can specify the control stops at the thread.start(), and carry out the action of printing several words to console.
Seems, BTrace is well designed to include versatile probes (annotations), including the synchronization operations.
I would give it a try before developing my own agents. If it is competent in my task, I will directly use it.
Otherwise, I might handle the refections (as in tamiflex) and develop my own agents.
Anyway, have a try on btrace first.
==============================
after trying the Btrace, I find it works badly, at least for my case.
Let us see their running example in the webpage: printing the message when a thread is started.
First, the annotation file:
// import all BTrace annotations
import com.sun.btrace.annotations.*;
// import statics from BTraceUtils class
import static com.sun.btrace.BTraceUtils.*;
// @BTrace annotation tells that this is a BTrace program
@BTrace
public class HelloWorld {
// @OnMethod annotation tells where to probe.
// In this example, we are interested in entry
// into the Thread.start() method.
@OnMethod(
clazz="java.lang.Thread",
method="start"
)
public static void func() {
// println is defined in BTraceUtils
// you can only call the static methods of BTraceUtils
println("about to start a thread!");
}
}Then, the program being instrumented:
public class Simple
{
static int sharedV= 0;
static int sharedM =0;
public static void main (String [] args)
{
System.out.println(Thread.currentThread().hashCode());
System.out.println("to start");
Thread t1 = new Thread(){
public void run()
{
System.out.println("started");
//System.out.println(Thread.currentThread().hashCode());
synchronized ("ss") {
sharedV =1;
sharedM =2;
sharedV =3;
sharedM =4;
}
}
};
Thread t2 = new Thread(){
public void run()
{
sharedM =10;
sharedV =20;
}
};
t1.start();
t2.start ();
try {
t1.join();
t2.join();
} catch (InterruptedException e) {
e.printStackTrace();
}
}
}
Now, we ollow their instruction to compile and run the instrumentation code.
1 btracec HelloWorld.java
2 btracer HelloWorld.class Simple
No output is printed.
I open the debug mode, and find that, the instrumentation inappropriately happens after the thread.start() statements.
From the trace information (in the following), the instrumentation happens after the thread.start() is executed, therefore, the instrumentation does not affect the thread.start() at all. To conclude, the agent fails to finish its task: instrumenting the thread.start() and printing information. The underlying reason is that, it does not provide a timely update. I have to develop my own agents... disappointed with Btrace.
Finally, I understand why there are so few information about Btrace on the internet.
扫一扫
9万+
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
