While using GDB to debug tests is straight forward, it's not immediately obvious that it can be done.
These notes should help developers debug their tests in a more methodical manner.
Details
Details
- Reviewers
schancel deadalnix - Group Reviewers
Restricted Project - Commits
- rSTAGING36765d789e83: Added developer-notes for debugging unit tests with GDB
rABC36765d789e83: Added developer-notes for debugging unit tests with GDB
I do this to debug tests and it works. :D
Diff Detail
Diff Detail
- Repository
- rABC Bitcoin ABC
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
doc/developer-notes.md | ||
---|---|---|
110 ↗ | (On Diff #3332) | Shouldn't that go under Development tips and tricks ? |
doc/developer-notes.md | ||
---|---|---|
110 ↗ | (On Diff #3332) | I guess it could, but I figured this section could be expanded over time. Either way works |
doc/developer-notes.md | ||
---|---|---|
110 ↗ | (On Diff #3332) | Considering there is a compiling for debugging in there, I think it should be moved. Because if you don't compile for debugging, then you'll have a very fund time with gdb. |
doc/developer-notes.md | ||
---|---|---|
121 ↗ | (On Diff #3332) | Maybe add: For OSX, use: cd /build/src/test lldb -- test_bitcoin break set --file interpreter.cpp --line 295 run |
doc/developer-notes.md | ||
---|---|---|
121 ↗ | (On Diff #3332) | Then maybe we just want to direct people to lldb (this works on linux as well). |
doc/developer-notes.md | ||
---|---|---|
121 ↗ | (On Diff #3332) | Thanks Matias! I've included both because people have differing levels of experience with different tools. |
doc/developer-notes.md | ||
---|---|---|
149 ↗ | (On Diff #3501) | I think files like this that are intended for newbies provide the most help when instructions are written out. |