The current code to display invalid memory accesses isn't terribly useful
as it doesn't tell you what address is actually being accessed. Include
it in the error message.
Signed-off-by: Mike Frysinger <vap...@gentoo.org>
---
memory.c | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/memory.c b/memory.c
index d528d1f..0ea0320 100644
--- a/memory.c
+++ b/memory.c
@@ -998,7 +998,9 @@ static uint64_t invalid_read(void *opaque,
target_phys_addr_t addr,
MemoryRegion *mr = opaque;
if (!mr->warning_printed) {
- fprintf(stderr, "Invalid read from memory region %s\n", mr->name);
+ fprintf(stderr,
+ "Invalid read from memory region %s at %#" TARGET_PRIxPHYS
"\n",
+ mr->name, addr);
mr->warning_printed = true;
}
return -1U;
@@ -1010,7 +1012,9 @@ static void invalid_write(void *opaque,
target_phys_addr_t addr, uint64_t data,
MemoryRegion *mr = opaque;
if (!mr->warning_printed) {
- fprintf(stderr, "Invalid write to memory region %s\n", mr->name);
+ fprintf(stderr,
+ "Invalid write to memory region %s at %#" TARGET_PRIxPHYS "\n",
+ mr->name, addr);
mr->warning_printed = true;
}
}
--
1.7.9.7
