diff options
| author | Luis Machado <luis.machado@arm.com> | 2023-06-06 10:57:59 +0100 |
|---|---|---|
| committer | Luis Machado <luis.machado@arm.com> | 2023-06-07 07:59:54 +0100 |
| commit | cb50f66e6ac7fa6dac664c10131e2c49fb94a591 (patch) | |
| tree | f80140990102a9063d9af29b1a3c84343fcbe09c | |
| parent | ba75d1c55cb42114e3bb5c8abe37e5c2bd657a02 (diff) | |
| download | gdb-cb50f66e6ac7fa6dac664c10131e2c49fb94a591.zip gdb-cb50f66e6ac7fa6dac664c10131e2c49fb94a591.tar.gz gdb-cb50f66e6ac7fa6dac664c10131e2c49fb94a591.tar.bz2 | |
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.
| -rw-r--r-- | gdb/printcmd.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/gdb/printcmd.c b/gdb/printcmd.c index f9517e6..d8d9749 100644 --- a/gdb/printcmd.c +++ b/gdb/printcmd.c @@ -3196,7 +3196,7 @@ memory_tag_check_command (const char *args, int from_tty) show_memory_tagging_unsupported (); if (args == nullptr) - error (_("Argument required (address or pointer)")); + error_no_arg (_("address or pointer")); /* Parse the expression into a value. If the value is an address or pointer, then check its logical tag against the allocation tag. */ |