zenithsiz/ftmemsim-valgrind
1
0
Fork 0
mirror of https://github.com/Zenithsiz/ftmemsim-valgrind.git synced 2026-02-03 10:05:29 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

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

Browse Source 
NEWS: who_point_at -> who_points_at
valgrind-monitor-def.py: MEN -> LEN
This commit is contained in:
Mark Wielaard 2023-04-26 21:31:13 +02:00
parent 15313a5580
commit f83f269dd1
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
NEWS
View File

@ -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>

2
coregrind/m_gdbserver/valgrind-monitor-def.py
View File

@ -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.