Andrew Cagney wrote:
> 
> > J. Johnston writes:
> >  > Elena Zannoni wrote:
> >  > >
> >  > > J. Johnston writes:
> >  > >  > The following patches mi-main.c to turn on the console output prefix prior
> >  > >  > to outputting the gdb startup messages.  The code checks for mi level
> >  > >  > and defers to old behavior for mi1.
> >  > >  >
> >  > >  > Ok to commit?
> >  > >  >
> >  > >
> >  > > Wouldn't this affect the testsuite as well?
> >  > > Or is this behavior not tested?
> >  > >
> >  > > Elena
> >  > >
> >  >
> >  > It does not affect the testsuite.  The testsuite startup code looks for
> >  > the gdb prompt or some form of error indication, but does not specifically
> >  > look at the start-up message.
> >  >
> >
> > Hmm, I wonder whether now it should. Since we are expecting a specific
> > behavior it might as well be tested. Thoughts?
> 
> It _needs_ to be tested - if it isn't tested it doesn't work :-)
> 
> Andrew

On that note, I have provided here a patch to the mi-support.exp file in
gdb/testsuite/lib.  It checks the startup message for mi and mi1 in
the mi startup routine.

I have also reincluded the code patch.  Please let me know if this is ok to
check in.

-- Jeff J.

gdb/testsuite/ChangeLog:

2002-11-06  Jeff Johnston  <jjohnstn@redhat.com>

	* lib/mi-support.exp (mi_gdb_start): Verify the startup message for mi1 and
	current mi is in correct format.  New mi startup message should be in
	console format.  This is part of fix for PR gdb/604.

gdb/mi/ChangeLog:

2002-11-06  Jeff Johnston  <jjohnstn@redhat.com>

	* mi-main.c (mi_command_loop): Initialize raw_stdout and gdb_stdout only if
	mi version is <= 1.
	(mi_init_ui): Initialize raw_stdout and gdb_stdout if mi version is > 1 so
	startup message is treated as console output.  This is part of fix for
	PR gdb/604.