search

rjust / defects4j

A Database of Real Faults and an Experimental Infrastructure to Enable Controlled Experiments in Software Engineering Research
MIT License
717 stars 299 forks source link

Some questions about suspicious statement #570

Closed HautGoduU closed 4 months ago

HautGoduU commented 4 months ago

Hello！ I'm sorry to bother you, I have some questions about defects4j for you, and I sincerely hope you can help and advise me.          (1) For a bug such as Math_57, I got some suspicious statements as shown in the figure by using the FL tool. But I found that the path of suspicious statement 1, for example, is not an absolute path, so how should I get the absolute path? Is it possible for a suspicious statement to exist in more than one path? Or, knowing the relative path to that suspicious statement, how should I find it and try to fix it？       (2) For a bug in defects4j such as math_50, which folder of the bug should be located by the FL and how should the FL get this information?          Thankyou for your busy schedule to read my letter . I would appreciate it if yougive me some help！ 6A43E97A-AFB1-4E9C-ADE3-6B689501FD3C

jose commented 4 months ago

This sounds to me like a GZoltar related question. I suggest you post it on GZoltar's repository.

rjust commented 4 months ago

@HautGoduU

To answer your question about paths in Defects4J, you can use the export command.

Here is an example for Math-50:

defects4j checkout -pMath -v50b -w/tmp/Math-50
...
defects4j export -p dir.src.classes -w/tmp/Math-50
Running ant (export.dir.src.classes)....................................... OK
src/main/java

The exported path is relative to the working directory, so you can concatenate the two to obtain the absolute path to the directory that contains the source files.

Best, René