X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=doc%2Fdebug.texi;h=402ede606345d07785666614a18748f6c3c114eb;hb=19becec31c5704572a3575336c57364d72fd572b;hp=aa833acbc07111d24c6126052f023958dd206d36;hpb=d158a7cd545fa8dd35dba91935029465eedff0da;p=pintos-anon diff --git a/doc/debug.texi b/doc/debug.texi index aa833ac..402ede6 100644 --- a/doc/debug.texi +++ b/doc/debug.texi @@ -99,6 +99,8 @@ of how your program got where it is, as a list of addresses inside the functions that were running at the time of the panic. You can also insert a call to @func{debug_backtrace}, prototyped in @file{}, to print a backtrace at any point in your code. +@func{debug_backtrace_all}, also declared in @file{}, +prints backtraces of all threads. The addresses in a backtrace are listed as raw hexadecimal numbers, which are difficult to interpret. We provide a tool called