Add a hint about using --no-isolate for GDB.
Change-Id: Ib9df5ed986a1c4082c9c7cd793a4d670be21ca66
This commit is contained in:
parent
355f3d0c12
commit
1af434cc02
1 changed files with 11 additions and 0 deletions
11
README.md
11
README.md
|
@ -257,6 +257,17 @@ First, build and run the host tests as usual (see above).
|
|||
The coverage report is now available at `covreport/index.html`.
|
||||
|
||||
|
||||
Attaching GDB to the tests
|
||||
--------------------------
|
||||
|
||||
Bionic's test runner will run each test in its own process by default to prevent
|
||||
tests failures from impacting other tests. This also has the added benefit of
|
||||
running them in parallel, so they are much faster.
|
||||
|
||||
However, this also makes it difficult to run the tests under GDB. To prevent
|
||||
each test from being forked, run the tests with the flag `--no-isolate`.
|
||||
|
||||
|
||||
LP32 ABI bugs
|
||||
-------------
|
||||
|
||||
|
|
Loading…
Reference in a new issue