OpenE2K/binutils-gdb
12
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

* gdbint.texinfo (Writing Tests): Mention gdb_test_multiple

Browse Source 
and tab expansion.
This commit is contained in:
Daniel Jacobowitz 2007-04-11 11:11:12 +00:00
parent b0b9258645
commit 8a3dae3ed0
2 changed files with 13 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
gdb/doc/ChangeLog
View File

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

9
gdb/doc/gdbint.texinfo
View File

@ -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