Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dev: add notes on creating breakpoints in autotest #5728

Merged
merged 1 commit into from
Jan 20, 2024
+8 −0
Merged

dev: add notes on creating breakpoints in autotest #5728

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions dev/source/docs/the-ardupilot-autotest-framework.rst
View file
Open in desktop
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