59baaabb89
We previously looked at the diff to the current head of the target branch, which may have moved in comparison to the merge base of a pull request. Thus we sometimes ended up with spurious clang-format errors, talking about changes introduced in another PR. |
||
---|---|---|
.. | ||
bash-autocomplete | ||
benchmark | ||
perf-test | ||
pretty-printers/gdb | ||
README.md | ||
build_doxygen.sh | ||
cadical-patch | ||
cbmc.spec | ||
compare_postprocessor_output.py | ||
cpplint.py | ||
diff_to_added_lines.py | ||
do_doc_convert.py | ||
doxy_merge_driver.sh | ||
expected_doxygen_warnings.txt | ||
filter_by_lines.py | ||
filter_expected_warnings.py | ||
format_classpath.sh | ||
generate_vcxproj | ||
glucose-syrup-patch | ||
glucose_CMakeLists.txt | ||
ls_parse.py | ||
make-rpm | ||
minisat-2.2.1-patch | ||
minisat2_CMakeLists.txt | ||
publish_doc.sh | ||
reformat_docs.py | ||
run_diff.sh | ||
run_doxygen.sh | ||
run_lint.sh | ||
string_table_check.sh | ||
travis_lint.sh | ||
vcxproj.1 | ||
vcxproj.2 |
README.md
A collection of utility scripts and script applications.
pretty-printers
GDB:
Pretty-printers for CBMC that enable easier debugging in IDEs and mitigate certain crashes due to the way some objects' memory is shared.
Currently it deals with:
- irep_idt
- dstring
- instructiont
To install:
- Navigate to /pretty-printers/gdb.
- Run install.py with python 3+.
- If an exception occurs, create an empty '.gdbinit' file in your home folder, and copy/paste the blob of code at the top of the install.py file.
The .gdbinit file is used by GDB during start-up to run any initial commands or scripts, and the code injects the pretty-printers during that.
Nothing else is required to get the pretty-printers to work, beside using GDB to debug the code.