Notes on ddb trace by corecode and TGEN

diff --git a/docs/howtos/HowToDebugVKernels/index.mdwn b/docs/howtos/HowToDebugVKernels/index.mdwn
index 23a4a45..8a51dc3 100644 (file)
--- a/docs/howtos/HowToDebugVKernels/index.mdwn
+++ b/docs/howtos/HowToDebugVKernels/index.mdwn
@@ -75,6 +75,9 @@ Let's get a trace of what went wrong:
     go_user(5709dd38,0,0,7b,0) at 0x82151ac
     db> 
 
+sys_ktrace, allproc_scan, etc represent the function names. The hex values in parentheses are the first five items on the stack.
+The last hex value is the instruction address. Since ddb doesn't really know how many arguments a function takes, it always prints five.
+
 # Gdb
 Quoting from vkernel(7):