Fedora audit log can be useful for tracing abnormal ends of programs.
# find abnormal ends (eg. segfaults) ausearch --message ANOM_ABEND # find entries related to a given user ausearch -ua 500 -i
Further info
Fedora audit log can be useful for tracing abnormal ends of programs.
# find abnormal ends (eg. segfaults) ausearch --message ANOM_ABEND # find entries related to a given user ausearch -ua 500 -i
Further info
Today I had to do a live debugging on a java application. I found a nice tool named btrace (no, it’s not that btrace…but THIS btrace ;).
Btrace seems magical:
Once downloaded, you have to:
Then run it, with:
# ./btrace -cp $YOUR_CLASSPATH Â $JVM_PID MyClassTracer.java
The MyClassTracer.java is something like this (example take from here):
import com.sun.btrace.annotations.*;
import static com.sun.btrace.BTraceUtils.*;
import java.io.File;
// every time new File(String) is called, print the file name
@BTrace
public class HelloBTrace {
@OnMethod(
clazz="java.io.File", method=""
)
public static void onNewFile(File self, String name) {
print("new file ");
println(name);
}
}