Better printing of out of range --dynamic-space-size arguments.

[sbcl.git] / doc / manual / support-and-bugs.texinfo

diff --git a/doc/manual/support-and-bugs.texinfo b/doc/manual/support-and-bugs.texinfo
index 5f6c6bd..a1a6426 100644 (file)
--- a/doc/manual/support-and-bugs.texinfo
+++ b/doc/manual/support-and-bugs.texinfo
@@ -15,7 +15,7 @@
 Your primary source of SBCL support should probably be the mailing
 list @strong{sbcl-help}: in addition to other users SBCL developers
 monitor this list and are available for advice. As an anti-spam
-measure subcription is required for posting:
+measure subscription is required for posting:
 
 @urlline{https://lists.sourceforge.net/lists/listinfo/sbcl-help}
 
@@ -56,21 +56,8 @@ available information - refer to the links they provide, the CREDITS
 file, mailing list archives, CVS commit messages, and so on. Please
 feel free to ask for advice on the sbcl-help list.
 
-@table @strong
-@item Christophe Rhodes
-is a long-time SBCL developer, available for custom programming.
-
-Email: @email{csr21@@cam.ac.uk}
-
-@item Steel Bank Studio Ltd
-provides commercial SBCL support and custom development, is run by
-SBCL developer @emph{Nikodemus Siivola}, and has another SBCL
-developer @emph{Richard Kreuter} as an affiliated consultant.
-
-Website: @url{http://sb-studio.net/}
-
-Email: @email{info@@sb-studio.net}
-@end table
+(At present, no companies or consultants wish to advertise paid support
+or custom SBCL development in this manual).
 
 @node Reporting Bugs
 @comment  node-name,  next,  previous,  up
@@ -126,7 +113,8 @@ send a useful bug report then:
 @enumerate
 
 @item
-Compile sbcl with ldb support (feature @code{:sb-ldb}, see
+@cindex ldb
+Compile SBCL with ldb support (feature @code{:sb-ldb}, see
 @file{base-target-features.lisp-expr}) and change @code{#define QSHOW_SIGNAL 0} to
 @code{#define QSHOW_SIGNAL 1} in @file{src/runtime/runtime.h}.
 
@@ -145,9 +133,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
@@ -157,6 +146,6 @@ stderr) produced by SBCL.
 Don't forget to include OS and SBCL version.
 
 @item
-If available include, information on outcome of the same test with
+If available, include information on outcome of the same test with
 other versions of SBCL, OS, ...
 @end enumerate