bugscpp
bugscpp copied to clipboard
A database of real-world C/C++ defaults to experiment in software engineering research
I tried to follow the steps in the README's Example section to execute some CLI commands, including make install, Displaying a List of Defects, Project Checkout, etc. However, when I...
Just like the reported libucl bug 3 and 5, libchewing project also contains redundant bugs. https://github.com/Suresoft-GLaDOS/bugscpp/blob/be5cc489cb2b3127ec3b73cb4adfdd290807f55b/bugscpp/taxonomy/libchewing/patch/0001-buggy.patch#L11-L24 https://github.com/Suresoft-GLaDOS/bugscpp/blob/be5cc489cb2b3127ec3b73cb4adfdd290807f55b/bugscpp/taxonomy/libchewing/patch/0002-buggy.patch#L11-L24
When I tried to checkout md4c-1, it produced API Error. This is the command I executed: `python3 bugscpp/bugscpp.py checkout md4c 1 -b` Output: ``` [md4c] cloning a new repository from...
- add gravity project using run_test.py - related commits - gravity 1- https://github.com/marcobambini/gravity/commit/63fa9bf0393dbbdfa1d4cb1f532df6e099f7c0b7 - gravity 2- https://github.com/marcobambini/gravity/commit/8cf6379645f458384fc44b627662de5345696072 - gravity 3- https://github.com/marcobambini/gravity/commit/9231f9e1a7d52712a06390ece55a30fe0d60677a
Hi `Suresoft-GLaDOS/defects4cpp`! This is a one-off automatically generated pull request from LGTM.com :robot:. You might have heard that we’ve integrated LGTM’s underlying CodeQL analysis engine natively into GitHub. The result...
They are [identically documented in the wiki](https://github.com/Suresoft-GLaDOS/bugscpp/wiki/libucl) and share the same vendored patches: https://github.com/Suresoft-GLaDOS/bugscpp/blob/85fb30ff15b7ad05267c23b4321c2427244cd52d/bugscpp/taxonomy/libucl/patch/0003-buggy.patch#L12-L22 https://github.com/Suresoft-GLaDOS/bugscpp/blob/85fb30ff15b7ad05267c23b4321c2427244cd52d/bugscpp/taxonomy/libucl/patch/0005-buggy.patch#L12-L22
I'm attempting to run tests for zsh using the following command: ``` python bugscpp/bugscpp.py test ./zsh/buggy-2 --coverage ``` However, even after 24 hours, not a single test case has been...
```sh # current status d++ checkout $PROJECT -b 1 -t $DIRECTORY_PATH_TO_WANT d++ build $REPOSITORY_PATH_TO_BUILD d++ test $REPOSITORY_PATH_TO_BUILD ``` Above code block is current d++ command. It felt uncomfortable to use....
When you run tests, you can specify output directory using --output-dir option Let's assume `test-result` is output directory. Test command is like below: ```python $ d++ test path\to\cppcheck\fixed#1 -v --output-dir=test-result...
#### Problem Location: `bugscpp/taxonomy/jerryscript/patch/0006-buggy.patch` The filename is misspelled in the `diff --git` line (`ecma-atomeics-object.c`). #### Correct line ```diff - diff --git a/jerry-core/ecma/operations/ecma-atomeics-object.c b/jerry-core/ecma/operations/ecma-atomics-object.c + diff --git a/jerry-core/ecma/operations/ecma-atomics-object.c b/jerry-core/ecma/operations/ecma-atomics-object.c