Toolchain/binutils-gdb
1
0
Fork 0
forked from Imagelibrary/binutils-gdb
Code Pull Requests Activity

Fix gdb.base/memtag.exp failure

Browse Source 
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.
This commit is contained in:
Luis Machado
2023-06-06 10:57:59 +01:00
parent ba75d1c55c
commit cb50f66e6a
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
gdb/printcmd.c
View File

@@ -3196,7 +3196,7 @@ memory_tag_check_command (const char *args, int from_tty)
show_memory_tagging_unsupported (); show_memory_tagging_unsupported ();
if (args == nullptr) 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 /* Parse the expression into a value. If the value is an address or
pointer, then check its logical tag against the allocation tag. */ pointer, then check its logical tag against the allocation tag. */