diff options
| author | Samuel Thibault <samuel.thibault@ens-lyon.org> | 2016-02-24 15:38:03 +0100 |
|---|---|---|
| committer | Samuel Thibault <samuel.thibault@ens-lyon.org> | 2016-02-24 15:38:03 +0100 |
| commit | e164cc3bc34b10fb415d146dcc1db3abe12fb1d2 (patch) | |
| tree | 07c1b67019f27b38ea71479f42c3fd783cf7415e | |
| parent | a20caca810a9e221e277cf0a94fa9793f00f2fc1 (diff) | |
note trace/u to get userland backtrace
| -rw-r--r-- | microkernel/mach/gnumach/debugging.mdwn | 6 |
1 files changed, 5 insertions, 1 deletions
diff --git a/microkernel/mach/gnumach/debugging.mdwn b/microkernel/mach/gnumach/debugging.mdwn index c14f6111..6511115a 100644 --- a/microkernel/mach/gnumach/debugging.mdwn +++ b/microkernel/mach/gnumach/debugging.mdwn @@ -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. |