Re: Fully anchor mi_gdb_test expected results.

[Daniel Jacobowitz <drow@false.org>]

On Wed, Aug 03, 2005 at 10:50:45PM -0400, Bob Rossi wrote:
> Hi,
> 
> This testsuite change simply does several simple things. First, when
> creating a new pty for the inferior, this change turn's terminal
> echo'ing off. This allows the expected results back from GDB/MI to not
> have to have the command sent to GDB in it. The surprising thing with 
> this change is that even when GDB shares the terminal's PTY with the 
> inferior, not putting the echo'd data in the expected command still
> works.
> 
> The only other notable change here is this,
> 
>    -   -re "\[\r\n\]*($pattern)\[\r\n\]+$mi_gdb_prompt\[ \]*$" {
>    +   -re "^(.*$pattern\[\r\n\]+$mi_gdb_prompt\[ \]*)$" {
> 
> that is the change that fully anchor's the output from GDB. The reason
> this is necessary is because with this change, I can grab the full
> response from GDB for a command. With this response I can do syntax
> checking with the parser that I wrote.
> 
> What does everyone think?

We're not using readline in this mode; we shouldn't have particularly
funny wrapping issues on the terminal, should we?  Can we match the
echoing instead of having to mess with stty?

Also, formatting on your comments again, please.

-- 
Daniel Jacobowitz
CodeSourcery, LLC