From: Tobias R. <tri...@us...> - 2010-03-28 17:44:57
|
Update of /cvsroot/sbcl/sbcl/doc/manual In directory sfp-cvsdas-3.v30.ch3.sourceforge.com:/tmp/cvs-serv15548/doc/manual Modified Files: support-and-bugs.texinfo Log Message: 1.0.37.12: Fix typo in "Reporting bugs" section of the manual. s/call_backtrace_from_fp/call backtrace_from_fp/ fixes lp#541771 (The last commit message contained a bogus commit version header of "1.0.37.6"; it was "1.0.37.11", of course.) Index: support-and-bugs.texinfo =================================================================== RCS file: /cvsroot/sbcl/sbcl/doc/manual/support-and-bugs.texinfo,v retrieving revision 1.1 retrieving revision 1.2 diff -u -d -r1.1 -r1.2 --- support-and-bugs.texinfo 3 Jun 2009 09:09:52 -0000 1.1 +++ support-and-bugs.texinfo 28 Mar 2010 17:44:49 -0000 1.2 @@ -145,9 +145,10 @@ @item If multiple threads are in play then still in gdb, try to get Lisp -backtrace for all threads: @code{thread apply all -call_backtrace_from_fp($ebp, 100)}. Substitute $ebp with $rbp on -x86-64. The backtraces will appear in the stdout of the SBCL process. +backtrace for all threads: @code{thread apply all call +backtrace_from_fp($ebp, 100)}. Substitute @code{$ebp} with @code{$rbp} +on x86-64. The backtraces will appear in the stdout of the SBCL +process. @item Send a report with the backtraces and the output (both stdout and |