aboutsummaryrefslogtreecommitdiff
path: root/gdb/fbsd-nat.c
diff options
context:
space:
mode:
authorAndrew Burgess <aburgess@redhat.com>2022-06-07 17:18:20 +0100
committerAndrew Burgess <aburgess@redhat.com>2022-06-08 20:04:33 +0100
commitdeb70aa0322c4c43b68fa859b52a0ccf2d904b0f (patch)
tree3bc994610ff5c28a529cf5b7838c8775444ba85f /gdb/fbsd-nat.c
parent5ca5b31d6381ba6d0309e6ae0b1527a852d08a4b (diff)
downloadfsf-binutils-gdb-deb70aa0322c4c43b68fa859b52a0ccf2d904b0f.zip
fsf-binutils-gdb-deb70aa0322c4c43b68fa859b52a0ccf2d904b0f.tar.gz
fsf-binutils-gdb-deb70aa0322c4c43b68fa859b52a0ccf2d904b0f.tar.bz2
gdb: remove trailing '.' from perror_with_name calls
I ran into this error while working on AArch64 GDB: Unable to fetch VFP registers.: Invalid argument. Notice the '.:' in the middle of this error message. This is because of this call in aarch64-linux-nat.c: perror_with_name (_("Unable to fetch VFP registers.")); The perror_with_name function take a string, and adds ': <message>' to the end the string, so I don't think the string that we pass to perror_with_name should end in '.'. This commit removes all of the trailing '.' characters from perror_with_name calls, which give more readable error messages. I don't believe that any of these errors are tested in the testsuite (after a little grepping).
Diffstat (limited to 'gdb/fbsd-nat.c')
-rw-r--r--gdb/fbsd-nat.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/gdb/fbsd-nat.c b/gdb/fbsd-nat.c
index 281b034..32b289f 100644
--- a/gdb/fbsd-nat.c
+++ b/gdb/fbsd-nat.c
@@ -94,7 +94,7 @@ fbsd_nat_target::find_memory_regions (find_memory_region_ftype func,
gdb::unique_xmalloc_ptr<struct kinfo_vmentry>
vmentl (kinfo_getvmmap (pid, &nitems));
if (vmentl == NULL)
- perror_with_name (_("Couldn't fetch VM map entries."));
+ perror_with_name (_("Couldn't fetch VM map entries"));
for (i = 0, kve = vmentl.get (); i < nitems; i++, kve++)
{