X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?p=pintos-anon;a=blobdiff_plain;f=doc%2Fdebug.texi;h=402ede606345d07785666614a18748f6c3c114eb;hp=aa833acbc07111d24c6126052f023958dd206d36;hb=28034001ef25d7ac4f58c7535a6fce767c9df8f5;hpb=8349a4cbeec56e4b497d98064ce51aba80c1f258

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{<debug.h>}, to print a backtrace at any point in your code.
+@func{debug_backtrace_all}, also declared in @file{<debug.h>}, 
+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