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.)

diff --git a/doc/manual/support-and-bugs.texinfo b/doc/manual/support-and-bugs.texinfo
index 5f6c6bd..a99ca6c 100644 (file)
--- a/doc/manual/support-and-bugs.texinfo
+++ b/doc/manual/support-and-bugs.texinfo
@@ -145,9 +145,10 @@ Attach gdb: @code{gdb -p <pidof sbcl>} and get backtraces for all threads:
 
 @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

diff --git a/version.lisp-expr b/version.lisp-expr
index 6978031..62fe67e 100644 (file)
--- a/version.lisp-expr
+++ b/version.lisp-expr
@@ -17,4 +17,4 @@
 ;;; checkins which aren't released. (And occasionally for internal
 ;;; versions, especially for internal versions off the main CVS
 ;;; branch, it gets hairier, e.g. "0.pre7.14.flaky4.13".)
-"1.0.37.11"
+"1.0.37.12"