Change Log

1.3.4

Implemented enhancements:

Fixed bugs:

@location(Kind.NEW) does not work with parameter annotated by @return #183
MethodInvocationRecorder may provide incomplete data in highly concurrent environment #180
RuntimeException while trying to printfield values #179
Problems with @return parameter #174
Location(kind = Kind.NEWARRAY) should support flexible "clazz" definition #173
Submitting compiled trace script via 'btrace' may not work #164
Inconsistent behavior when trying to probe return values from multiple methods #145

Closed issues:

BTrace is crashing the applications that is attached with #177
SIGSEGV in the main process #172
how to run multiple btrace scripts for the same application. #171
how to trace a application which is run by using a tcserver which runs tomcat inbuilt #169
null pointer exception and illegalstateexception while tracing an application #168
connection refused or well-known file is not secure #167
unable to open socket file: target process not responding or hotspot vm not loaded #166
default trace ouput file created by btracer command is not generating when used in linux terminal #165
@onexit not handled properly after #154 #161
Omitting the 'method' argument in @OnMethod counter-intuitively performs match against the handler method name #159
Tracing all methods of all available classes can make BTrace crash #154
@duration annotation refused for Kind.CALL #153
@onerror requires full Throwable type in the handler method signature #152
default trace ouput file created by btracer command is not generating when used in linux terminal #151
tracing a *.jar files from command prompt #150
Unable to open socket file: target process not responding or HotSpot VM not loaded #139

Merged pull requests: