* gdbint.texinfo (Writing Tests): Mention gdb_test_multiple

	and tab expansion.

diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index e8e75d8..70bf1f8 100644 (file)
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -1,3 +1,8 @@
+2007-04-11  Daniel Jacobowitz  <dan@codesourcery.com>
+
+       * gdbint.texinfo (Writing Tests): Mention gdb_test_multiple
+       and tab expansion.
+
 2007-04-10  Daniel Jacobowitz  <dan@codesourcery.com>
 
        * gdbint.texinfo (SOM): Correct location of the SOM reader.

diff --git a/gdb/doc/gdbint.texinfo b/gdb/doc/gdbint.texinfo
index b981e80..8e6720f 100644 (file)
--- a/gdb/doc/gdbint.texinfo
+++ b/gdb/doc/gdbint.texinfo
@@ -7144,7 +7144,14 @@ instance, @file{gdb.base/exprs.exp} defines a @code{test_expr} that
 calls @code{gdb_test} multiple times.
 
 Only use @code{send_gdb} and @code{gdb_expect} when absolutely
-necessary, such as when @value{GDBN} has several valid responses to a command.
+necessary.  Even if @value{GDBN} has several valid responses to
+a command, you can use @code{gdb_test_multiple}.  Like @code{gdb_test},
+@code{gdb_test_multiple} recognizes internal errors and unexpected
+prompts.
+
+Do not write tests which expect a literal tab character from @value{GDBN}.
+On some operating systems (e.g.@: OpenBSD) the TTY layer expands tabs to
+spaces, so by the time @value{GDBN}'s output reaches expect the tab is gone.
 
 The source language programs do @emph{not} need to be in a consistent
 style.  Since @value{GDBN} is used to debug programs written in many different