Fix typos in NEWS and valgrind-monitor-def.py

NEWS: who_point_at -> who_points_at
valgrind-monitor-def.py: MEN -> LEN

diff --git a/NEWS b/NEWS
index 7974f0c2e93cc80b88df0693b1afb785c1469437..d9e04ab823d64f1fc072fa37f19ca46191eaa9e3 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -26,7 +26,7 @@ AMD64/macOS 10.13 and nanoMIPS/Linux.
   to pass it to a subsequent monitor command, the GDB front end
   command will evaluate the address argument. It is for example
   possible to do:
-    (gdb) memcheck who_point_at &some_struct sizeof(some_struct)
+    (gdb) memcheck who_points_at &some_struct sizeof(some_struct)
   instead of:
     (gdb) p &some_struct
     $2 = (some_struct_type *) 0x1130a0 <some_struct>

diff --git a/coregrind/m_gdbserver/valgrind-monitor-def.py b/coregrind/m_gdbserver/valgrind-monitor-def.py
index da617cb8505a8e8783bc8077c261e9a15a226594..b4e7b992dc984d74d0bf5cb8222a53e0cd6dccd4 100644 (file)
--- a/coregrind/m_gdbserver/valgrind-monitor-def.py
+++ b/coregrind/m_gdbserver/valgrind-monitor-def.py
@@ -717,7 +717,7 @@ where HEUR is one of:
 @Vinit("memcheck", "who_points_at", gdb.COMMAND_DATA, gdb.COMPLETE_EXPRESSION, False)
 class Memcheck_Who_Points_At_Command(Valgrind_ADDR_LEN_opt):
     """Show places pointing inside LEN (default 1) bytes at ADDR.
-Usage: memcheck who_points_at ADDR [MEN]
+Usage: memcheck who_points_at ADDR [LEN]
 With LEN 1, only shows "start pointers" pointing exactly to ADDR.
 With LEN > 1, will also show "interior pointers"
 ADDR is an address expression evaluated by GDB.