From 582fc286ae8138cba558d1e8c75209ae251f4105 Mon Sep 17 00:00:00 2001 From: Remzi Arpaci-Dusseau Date: Sat, 17 Sep 2022 04:05:23 -0500 Subject: [PATCH] added more tips --- initial-xv6-tracer/README.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/initial-xv6-tracer/README.md b/initial-xv6-tracer/README.md index cb73b31..f611a31 100644 --- a/initial-xv6-tracer/README.md +++ b/initial-xv6-tracer/README.md @@ -74,6 +74,11 @@ the tracing. Then finally figure out how to do the tracing. **cprintf()** can be used in the kernel to print out debugging info. +You may need to implement some routines in the kernel, such as **strcmp()** +and **strcpy()**, to implement these system calls. You can always copy +the definitions of these routines from **ulib.c** (this is where they +are defined for user processes). + Using gdb (the debugger) may be helpful in understanding code, doing code traces, and is helpful for later projects too. Get familiar with this fine tool!