From 8181f0045df765a7f28db745f4a8bd3c5a1da82d Mon Sep 17 00:00:00 2001 From: Luis Machado Date: Thu, 17 Nov 2022 10:19:30 +0000 Subject: Document the memory_tagged argument for memory region callbacks There were no comments in some instances (gdb/defs.h, gdb/core.c and gdb/linux-tdep.c), so address that by adding comments where those are missing. --- gdb/defs.h | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) (limited to 'gdb/defs.h') diff --git a/gdb/defs.h b/gdb/defs.h index 0d9a39a..f51ab9e 100644 --- a/gdb/defs.h +++ b/gdb/defs.h @@ -340,8 +340,12 @@ extern const char *pc_prefix (CORE_ADDR); /* * Process memory area starting at ADDR with length SIZE. Area is readable iff READ is non-zero, writable if WRITE is non-zero, executable if EXEC is non-zero. Area is possibly changed against - its original file based copy if MODIFIED is non-zero. DATA is - passed without changes from a caller. */ + its original file based copy if MODIFIED is non-zero. + + MEMORY_TAGGED is true if the memory region contains memory tags, false + otherwise. + + DATA is passed without changes from a caller. */ typedef int (*find_memory_region_ftype) (CORE_ADDR addr, unsigned long size, int read, int write, int exec, -- cgit v1.1