aboutsummaryrefslogtreecommitdiff
path: root/cpu
diff options
context:
space:
mode:
authorAndrew Burgess <aburgess@redhat.com>2024-04-15 14:10:05 +0100
committerAndrew Burgess <aburgess@redhat.com>2024-04-17 13:34:30 +0100
commit6e4f0b3ea0d49c4fd11002a8074eb49e7838b4b2 (patch)
tree06fb98a942107b807582aa083539a434bf1816a7 /cpu
parentc25c939387cfc378c01fb5eb7f49c78c03b8cdcb (diff)
downloadgdb-6e4f0b3ea0d49c4fd11002a8074eb49e7838b4b2.zip
gdb-6e4f0b3ea0d49c4fd11002a8074eb49e7838b4b2.tar.gz
gdb-6e4f0b3ea0d49c4fd11002a8074eb49e7838b4b2.tar.bz2
gdb/record: add an assert in cmd_record_start
The 'record' command is both a prefix command AND an alias for 'target record-full'. As it is a prefix command, if a user types: (gdb) record blah Then GDB will look for, and try to invoke the 'blah' sub-command. This will either succeed (if blah is found) or throw an error (if blah is not found). As such, the only way to invoke the 'record' command is like: (gdb) record It is impossible to pass arguments to the 'record' command. As we know this is true then we can assert this in cmd_record_start. I added this assert because initially I was going to try forwarding ARGS from cmd_record_start to the 'target record-full' command, but then I realised passing arguments to 'record' was impossible. There should be no user visible changes after this commit. Approved-By: Tom Tromey <tom@tromey.com>
Diffstat (limited to 'cpu')
0 files changed, 0 insertions, 0 deletions