Skip to content

Mention that tests need a Python-enabled gdb. #243

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

Merged
merged 3 commits into from
Dec 3, 2018
Merged

Mention that tests need a Python-enabled gdb. #243

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
51d1ad6
Mention that tests need a Python-enabled gdb.
vext01 Nov 27, 2018
e24bce4
Explain how to check if gdb supports Python.
vext01 Dec 3, 2018
80ae2c6
Provide a Python example.
vext01 Dec 3, 2018
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
6 changes: 6 additions & 0 deletions src/tests/running.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,12 @@ timestamp file for every test can be found under `build/ARCH/test/`.
To force-rerun a test (e.g. in case the test runner fails to notice
a change) you can simply remove the timestamp file.

Note that some tests require a Python-enabled gdb. You can test if
your gdb install supports Python by using the `python` command from
within gdb (type some Python code followed by `CTRL+D` to execute it).
If you are building gdb from source, you need to configure with
`--with-python=<path-to-python-binary>`.

## Running a subset of the test suites

When working on a specific PR, you will usually want to run a smaller
Expand Down