Skip to content

Commit

Permalink
dev: add notes on creating breakpoints in autotest
Browse files Browse the repository at this point in the history
  • Loading branch information
peterbarker authored and Hwurzburg committed Jan 20, 2024
1 parent 942b5f7 commit 0a6be80
Showing 1 changed file with 8 additions and 0 deletions.
8 changes: 8 additions & 0 deletions dev/source/docs/the-ardupilot-autotest-framework.rst
Original file line number Diff line number Diff line change
Expand Up @@ -138,12 +138,20 @@ AutoTest can run the ArduPilot binary under gdb:

In an X Windowing System environment, an xterm window will contain the GDB terminal; stderr from the ArduPilot binary will also appear in this window. Where X is not available but `GNU screen <https://www.gnu.org/software/screen/>`__ is, a detached screen will be created with the same content.

You can insert breakpoints on the command-line (use multiple times to insert multiple breakpoints):

::

./Tools/autotest/autotest.py --no-clean --gdb --debug -B Copter::update build.Copter test.Copter

You can insert a Python method call into your test to cause the autopilot to enter the attached debugger:

::

self.send_debug_trap()

This feature works well when combined with the ``--disable-breakpoints`` command-line option as you can enable the breakpoints when the debug trap is sent.

Using with Valgrind
...................

Expand Down

0 comments on commit 0a6be80

Please sign in to comment.