diff options
| author | Alan Hayward <alan.hayward@arm.com> | 2019-05-17 14:35:23 +0100 |
|---|---|---|
| committer | Alan Hayward <alan.hayward@arm.com> | 2019-05-17 14:35:55 +0100 |
| commit | 29b523140ecf72bc3fdf570c71fbda6fe85cf930 (patch) | |
| tree | e646b922006aac57b873ce1099beef6b45d4e46a /gdb/testsuite/gdb.threads/pending-step.c | |
| parent | ca1285d17534cff3041c07ac7841288e1b3ba19c (diff) | |
| download | gdb-29b523140ecf72bc3fdf570c71fbda6fe85cf930.zip gdb-29b523140ecf72bc3fdf570c71fbda6fe85cf930.tar.gz gdb-29b523140ecf72bc3fdf570c71fbda6fe85cf930.tar.bz2 | |
testsuite: Add option to capture GDB debug
Add both board option and environment variable which enables gdb
debug via a comma separated list and sends it to the file gdb.debug,
located in the output directory for the current test. Document this.
Add support for the environment variable in the Makefile.
The testsuite can be run with gdb debug enabled in the following way:
make check GDB_DEBUG="infrun,target,remote"
A Test with multiple invocations of GDB will all append debug to the
same log file.
gdb/testsuite/ChangeLog:
* Makefile.in: Pass through GDB_DEBUG.
* README (Testsuite Parameters): Add GDB_DEBUG.
(gdb,debug): Add board setting.
* lib/gdb.exp (default_gdb_start): Start debugging.
(gdb_debug_enabled): New procedure.
(gdb_debug_init): Likewise.
Diffstat (limited to 'gdb/testsuite/gdb.threads/pending-step.c')
0 files changed, 0 insertions, 0 deletions