The bashdb is definitely an awesome gdb-like terminal debugger with rich features such as syntax hightlighting, variable watch. However, it lacks the feature to preset breakpoints in a per-project file like pdb. Enabling such feature will be tremendously useful to trouble shoot complex bash projects where locating the right lines of code for debugging is non-trivial task. This issue proposes the preset breakpoints in a file named .bashdbrc with statements similar to the Python's pdb:
# b awq/quantize/quantizer.py:156
# b awq/quantize/quantizer.py:339
b /home/user/work/AutoAWQ/awq/quantize/quantizer.py:117
The .bashdbrc should allow user to:
- leave comments to note reason for configuration change
- set line based unconditional breakpoints
- set conditional breakpoints with boolean expression at the end
Besides breakpoints, it would be nice to support additional settings in the .bashdbrc file. And a two-level .bashdbrc scheme could be adopted:
- The
~/.bashdbrc stores common settings
- The per project
./.bashdbrc overrides the per user settings
Thanks for considering this feature request!
The bashdb is definitely an awesome gdb-like terminal debugger with rich features such as syntax hightlighting, variable watch. However, it lacks the feature to preset breakpoints in a per-project file like pdb. Enabling such feature will be tremendously useful to trouble shoot complex bash projects where locating the right lines of code for debugging is non-trivial task. This issue proposes the preset breakpoints in a file named
.bashdbrcwith statements similar to the Python's pdb:The
.bashdbrcshould allow user to:Besides breakpoints, it would be nice to support additional settings in the
.bashdbrcfile. And a two-level.bashdbrcscheme could be adopted:~/.bashdbrcstores common settings./.bashdbrcoverrides the per user settingsThanks for considering this feature request!