microbat
microbat copied to clipboard
llmhyy
A feedback-based debugger for interactively recommending suspicious step in buggy program execution.
Sometimes, it takes a lot of time to conduct control mending and library search
I append found case as follows: Math | 13 | org.apache.commons.math3.optimization.fitting.PolynomialFitterTest#testLargeSample Math | 14 | org.apache.commons.math3.fitting.PolynomialFitterTest#testLargeSample Math | 38 | org.apache.commons.math.optimization.direct.BOBYQAOptimizerTest#testConstrainedRosenWithMoreInterpolationPoints Closure | 26 | com.google.javascript.jscomp.ProcessCommonJSModulesTest#testWithoutExports Mockito | 5 |...
We may need to separate the trace, variable, and step-variable relation into different trace files so that we can handle the case when the trace length is over long. I...
In case of the bug is an infinite loop bug like Lang-43, we can run the fixed trace first, then give a step_limit for the buggy trace (maybe twice the...
hi @lylytran As discussed, we may need to refactor the bytecode method. Let's have a skeleton first. I will look into the details.
The 280th step of fixed trace of Lang-56 writes a field curPut which should be null (the same as 280th step in the buggy trace) but it is assigned with...
hi @lylytran Would you please kindly check the following command line for Mockito-6? The program behaves differently with and without instrumentation. cmd with instrumentation: ``` E:\linyun\bug_repo\jdk1.7.0_800\bin\java -Xmx30g -ea -noverify -javaagent:E:\linyun\software\eclipse-java-mars\eclipse-java-mars-clean\eclipse\dropins\junit_lib\instrumentator.jar=precheck=false,excludes=java.util.Properties*,java_home=E:\linyun\bug_repo\jdk1.7.0_800,stepLimit=100000,log=printProgress;info,working_dir=E:\linyun\bug_repo\Mockito\6\bug,varLayer=1,launch_class=org.mockitousage.matchers.AnyXMatchersAcceptNullsTest,class_path=E:\linyun\bug_repo\Mockito\6\bug\build\classes\test;E:\linyun\bug_repo\Mockito\6\bug\build\classes\main;E:\linyun\bug_repo\Mockito\6\bug\lib\build\ant-googlecode-0.0.3.jar;E:\linyun\bug_repo\Mockito\6\bug\lib\build\ant4hg-V0.07.jar;E:\linyun\bug_repo\Mockito\6\bug\lib\build\asm-3.1.jar;E:\linyun\bug_repo\Mockito\6\bug\lib\build\bnd-0.0.313.jar;E:\linyun\bug_repo\Mockito\6\bug\lib\build\jarjar-1.0.jar;E:\linyun\bug_repo\Mockito\6\bug\lib\build\jaxen-1.1.1.jar;E:\linyun\bug_repo\Mockito\6\bug\lib\build\maven-ant-tasks-2.0.9.jar;E:\linyun\bug_repo\Mockito\6\bug\lib\build\pmd-4.1.jar;E:\linyun\bug_repo\Mockito\6\bug\lib\build\sorcerer.jar;E:\linyun\bug_repo\Mockito\6\bug\lib\repackaged\cglib-and-asm-1.0.jar;E:\linyun\bug_repo\Mockito\6\bug\lib\run\com.springsource.org.hamcrest.core-1.1.0.jar;E:\linyun\bug_repo\Mockito\6\bug\lib\run\objenesis-2.1.jar;E:\linyun\bug_repo\Mockito\6\bug\lib\sources\cglib-and-asm-1.0-sources.jar;E:\linyun\bug_repo\Mockito\6\bug\lib\sources\com.springsource.org.hamcrest.core-1.1.0-sources.jar;E:\linyun\bug_repo\Mockito\6\bug\lib\sources\objenesis-2.1-sources.jar;E:\linyun\bug_repo\Mockito\6\bug\lib\test\fest-assert-1.3.jar;E:\linyun\bug_repo\Mockito\6\bug\lib\test\fest-util-1.1.4.jar;E:\linyun\bug_repo\Mockito\6\bug\lib\test\powermock-reflect-1.2.5.jar;E:\linyun\bug_repo\Mockito\6\bug\build\libs\mockito-core-2.0.0-beta.jar;E:\linyun\bug_repo\Mockito\lib\objenesis-1.2.jar;E:\linyun\software\eclipse-java-mars\eclipse-java-mars-clean\eclipse\dropins\junit_lib\junit.jar;E:\linyun\software\eclipse-java-mars\eclipse-java-mars-clean\eclipse\dropins\junit_lib\org.hamcrest.core.jar;E:\linyun\software\eclipse-java-mars\eclipse-java-mars-clean\eclipse\dropins\junit_lib\testrunner.jar;E:\linyun\software\eclipse-java-mars\eclipse-java-mars-clean\eclipse\dropins\junit_lib\bcel-6.0.jar;E:\linyun\software\eclipse-java-mars\eclipse-java-mars-clean\eclipse\dropins\junit_lib\javassist.jar,dump_file_path=E:\linyun\software\eclipse-java-mars\eclipse-java-mars-clean\eclipse\trace\Mockito\6\bug.exec,expectedSteps=7579...
In Closure-83, the control dominator of step 287 in the buggy trace is incorrect. In addition, step 287 should not be considered as the observed fault.
hi @lylytran The documents are very important to maintain the projects. For now the code volume is kind of large. I believe that the code cannot be run when any...