Fix gdb.base/memtag.exp failure
authorLuis Machado <luis.machado@arm.com>
Tue, 6 Jun 2023 09:57:59 +0000 (10:57 +0100)
committerLuis Machado <luis.machado@arm.com>
Wed, 7 Jun 2023 06:59:54 +0000 (07:59 +0100)
commitcb50f66e6ac7fa6dac664c10131e2c49fb94a591
treef80140990102a9063d9af29b1a3c84343fcbe09c
parentba75d1c55cb42114e3bb5c8abe37e5c2bd657a02
Fix gdb.base/memtag.exp failure

While running this test on an emulator, I noticed we're failing to match the
output message when "memory-tag check" is issued with no arguments.  That's
because I coded the message using "error" and missed a period at the end.  Other
similar messages are issued with error_no_arg.

This patch changes that call to use error_no_arg.

Tested on aarch64-linux Ubuntu 20.04/22.04.
gdb/printcmd.c