diff options
Diffstat (limited to 'microkernel/mach/gnumach/debugging.mdwn')
| -rw-r--r-- | microkernel/mach/gnumach/debugging.mdwn | 12 |
1 files changed, 8 insertions, 4 deletions
diff --git a/microkernel/mach/gnumach/debugging.mdwn b/microkernel/mach/gnumach/debugging.mdwn index c5c592b7..164c4349 100644 --- a/microkernel/mach/gnumach/debugging.mdwn +++ b/microkernel/mach/gnumach/debugging.mdwn @@ -1,5 +1,5 @@ -[[!meta copyright="Copyright © 2007, 2008, 2009, 2011, 2012, 2013, 2014 Free -Software Foundation, Inc."]] +[[!meta copyright="Copyright © 2007, 2008, 2009, 2011, 2012, 2013, 2014, 2016 +Free Software Foundation, Inc."]] [[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable id="license" text="Permission is granted to copy, distribute and/or modify this @@ -14,7 +14,7 @@ Here are some hints to debug with GNU Mach. [[!toc levels=2]] -# Kernel Debugger +# Kernel Debugger (KDB) Mach has a built-in kernel debugger. [Manual](http://www.gnu.org/software/hurd/gnumach-doc/Kernel-Debugger.html). @@ -45,11 +45,15 @@ Run the addr2line tool on the return addresses: This will print the source code lines of the backtrace. +To get the userland backtrace of the thread, you can use + + trace/u + To examine the backtrace of some given thread, use show all thread/u -to get the whole listing of all tasks and threads. You can then use trace/t to trace a specific thread. +to get the whole listing of all tasks and threads. You can then use trace/t or trace/tu to trace a specific thread. Unfortunately, userland and kernelland use the same range of addresses, so one can not get userland traces easily. The Xen port uses different ranges, and in that case one can use trace/u to also get the userland trace. |