From 95aebe191e10c4fd568ecf554a96038ef6004e72 Mon Sep 17 00:00:00 2001 From: tracer-ysyx Date: Wed, 13 Mar 2024 18:03:12 +0800 Subject: [PATCH] =?UTF-8?q?>=20compile=20NEMU=20ysyx=5F22040000=20?= =?UTF-8?q?=E6=9D=8E=E5=BF=83=E6=9D=A8=20Linux=20calcite=206.6.19=20#1-Nix?= =?UTF-8?q?OS=20SMP=20PREEMPT=5FDYNAMIC=20Fri=20Mar=20=201=2012:35:11=20UT?= =?UTF-8?q?C=202024=20x86=5F64=20GNU/Linux=20=2018:03:12=20=20up=20=20=207?= =?UTF-8?q?:39,=20=202=20users,=20=20load=20average:=200.78,=200.67,=200.5?= =?UTF-8?q?5?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- nemu/Kconfig | 2 +- nemu/src/memory/paddr.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/nemu/Kconfig b/nemu/Kconfig index adc8183..cd9b909 100644 --- a/nemu/Kconfig +++ b/nemu/Kconfig @@ -164,7 +164,7 @@ config MTRACE config MTRACE_RANGE depends on MTRACE string "Memory trace active range" - default "0-fffffff" + default "0-0xfffffff" help Memory tracer will only print memory access in these ranges. Use comma to seperate between ranges. diff --git a/nemu/src/memory/paddr.c b/nemu/src/memory/paddr.c index d34fec6..b694c85 100644 --- a/nemu/src/memory/paddr.c +++ b/nemu/src/memory/paddr.c @@ -69,7 +69,7 @@ void init_mem() { ptr = strtok_r(range, ",", &saveptr); for (range_count = 0; range_count < CONFIG_MTRACE_RANGE_MAX; ) { word_t start, end; - Assert(sscanf(ptr, FMT_WORD "-" FMT_WORD, &start, &end) == 2, "Config option MTRACE_RANGE has wrong format"); + Assert(sscanf(ptr, FMT_PADDR "-" FMT_PADDR, &start, &end) == 2, "Config option MTRACE_RANGE has wrong format"); mtrace_start[range_count] = start; mtrace_end[range_count] = end;