binutils-gdb/gdb/testsuite/gdb.btrace/multi-inferior.exp

80 lines
2.2 KiB
Plaintext
Raw Normal View History

# This testcase is part of GDB, the GNU debugger.
#
# Copyright 2020-2021 Free Software Foundation, Inc.
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 3 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program. If not, see <http://www.gnu.org/licenses/>.
# Test that recording is per-inferior.
#
# When recording an inferior, threads from other inferiors, both existing
# and newly created, are not automatically recorded.
#
# Each inferior can be recorded separately.
if { [skip_btrace_tests] } {
unsupported "target does not support record-btrace"
return -1
}
if { [use_gdb_stub] } {
unsupported "test creates multiple inferiors"
return -1
}
standard_testfile
if [prepare_for_testing "failed to prepare" $testfile {} {debug}] {
return -1
}
with_test_prefix "inferior 1" {
if ![runto_main] {
untested "failed to run to main"
return -1
}
}
with_test_prefix "inferior 2" {
gdb_test "add-inferior -exec ${binfile}" "Added inferior 2.*" \
"add second inferior"
gdb_test "inferior 2" "Switching to inferior 2.*"
if ![runto_main] {
untested "inferior 2: failed to run to main"
return -1
}
gdb_test_no_output "record btrace" "record btrace"
}
with_test_prefix "inferior 1" {
gdb_test "inferior 1" "Switching to inferior 1.*"
gdb, record: rephrase the 'not recording' error message When trying to use one of the record commands without having enabled recording first, GDB gives the error message: (gdb) record function-call-history No record target is currently active. Use one of the "target record-<TAB><TAB>" commands first. In the record help, however, we say: (gdb) help record record, rec Start recording. List of record subcommands: record btrace, record b -- Start branch trace recording. record delete, record del, record d -- Delete the rest of execution log and start recording it anew. record full -- Start full execution recording. record function-call-history -- Prints the execution history at function granularity. record goto -- Restore the program to its state at instruction number N. record instruction-history -- Print disassembled instructions stored in the execution log. record save -- Save the execution log to a file. record stop, record s -- Stop the record/replay target. Change the above error message to (gdb) record function-call-history No recording is currently active. Use the "record full" or "record btrace" command first. to align with the help text. gdb/ChangeLog: 2020-12-03 Markus Metzger <markus.t.metzger@intel.com> * record.c (require_record_target): Rephrase error message. (info_record_command): Likewise. gdb/testsuite/ChangeLog: 2020-12-03 Markus Metzger <markus.t.metzger@intel.com> * gdb.btrace/enable.exp: Update error message. * gdb.btrace/multi-inferior.exp: Likewise. * gdb.btrace/reconnect.exp: Likewise. * gdb.python/py-record-btrace.exp: Likewise. * gdb.python/py-record-full.exp: Likewise.
2020-12-04 00:04:29 +08:00
gdb_test "info record" "No recording is currently active\\."
gdb_test_no_output "record btrace" "record btrace"
}
with_test_prefix "inferior 3" {
gdb_test "add-inferior -exec ${binfile}" "Added inferior 3.*" \
"add third inferior"
gdb_test "inferior 3" "Switching to inferior 3.*"
if ![runto_main] {
untested "inferior 3: failed to run to main"
return -1
}
gdb, record: rephrase the 'not recording' error message When trying to use one of the record commands without having enabled recording first, GDB gives the error message: (gdb) record function-call-history No record target is currently active. Use one of the "target record-<TAB><TAB>" commands first. In the record help, however, we say: (gdb) help record record, rec Start recording. List of record subcommands: record btrace, record b -- Start branch trace recording. record delete, record del, record d -- Delete the rest of execution log and start recording it anew. record full -- Start full execution recording. record function-call-history -- Prints the execution history at function granularity. record goto -- Restore the program to its state at instruction number N. record instruction-history -- Print disassembled instructions stored in the execution log. record save -- Save the execution log to a file. record stop, record s -- Stop the record/replay target. Change the above error message to (gdb) record function-call-history No recording is currently active. Use the "record full" or "record btrace" command first. to align with the help text. gdb/ChangeLog: 2020-12-03 Markus Metzger <markus.t.metzger@intel.com> * record.c (require_record_target): Rephrase error message. (info_record_command): Likewise. gdb/testsuite/ChangeLog: 2020-12-03 Markus Metzger <markus.t.metzger@intel.com> * gdb.btrace/enable.exp: Update error message. * gdb.btrace/multi-inferior.exp: Likewise. * gdb.btrace/reconnect.exp: Likewise. * gdb.python/py-record-btrace.exp: Likewise. * gdb.python/py-record-full.exp: Likewise.
2020-12-04 00:04:29 +08:00
gdb_test "info record" "No recording is currently active\\."
gdb_test_no_output "record btrace" "record btrace"
}