diff options
| author | Christina Schimpe <christina.schimpe@intel.com> | 2024-11-26 08:06:37 -0800 |
|---|---|---|
| committer | Christina Schimpe <christina.schimpe@intel.com> | 2025-01-07 14:05:56 +0000 |
| commit | a65684f7c4065667a2ace6bffaf6a08951c153bb (patch) | |
| tree | ea9da9135fb4f1ea69605cd9ad6ed189c412f14d /gprofng/src | |
| parent | 844afe8d0e5bc95ad48dd46d6adcdc350f598b7d (diff) | |
| download | binutils-a65684f7c4065667a2ace6bffaf6a08951c153bb.zip binutils-a65684f7c4065667a2ace6bffaf6a08951c153bb.tar.gz binutils-a65684f7c4065667a2ace6bffaf6a08951c153bb.tar.bz2 | |
testsuite: adapt to new --debug command line option
Since commit "gdbserver: allow the --debug command line option to take a
value", gdbserver no longer supports
--debug
--remote-debug
--event-loop-debug.
Instead, --debug now takes a comma separated list of components.
The make check parameter GDBSERVER_DEBUG doesn't support these changes
yet. This patch fixes this, by adding the --debug gdbserver arguments,
as "debug-threads", "debug-remote", "debug-event-loop" or "debug-all" for
GDBSERVER_DEBUG. Replay logging is still enabled by adding the
"replay" GDBSERVER_DEBUG argument. We can also configure "all" to
enable all of the available options.
Now, for instance, we can use it as follows:
make check GDBSERVER_DEBUG="debug-remote,debug-event-loop,replay" RUNTESTFLAGS="--target_board=native-gdbserver" TESTS="gdb.trace/ftrace.exp"
or simply
make check GDBSERVER_DEBUG="all" RUNTESTFLAGS="--target_board=native-gdbserver" TESTS="gdb.trace/ftrace.exp"
to enable all debug options.
Approved-By: Tom Tromey <tom@tromey.com>
Diffstat (limited to 'gprofng/src')
0 files changed, 0 insertions, 0 deletions