Description of problem:

GDB when used with the MI interpreter outputs the following message, when the inferior is restarted after a new version of the image of the inferior is generated:

"Missing separate debuginfos, use: debuginfo-install gcc.i386 glib2.i386 glibc.i686 glibmm24.i386 libgtop2.i386 libselinux.i386 libsigc++20.i386 libxml2.i386 zlib.i386"

The problem with that string is that it does not comply with the GDB/MI format, so it breaks GDB/MI clients.

Basically, each line of the message should be preceded by a '~' character, then by a '"' character, and the line should be ended by the '\n"' string.


Version-Release number of selected component (if applicable):

gdb-6.8-17.fc9

How reproducible:

Allways.

Steps to Reproduce:

1. compile a program file foo.c into a program foo.
2. gdb --interpreter=mi2 foo
3. break main
4. -exec-run
5. in another shell, do: 
touch foo.c;
recompile foo.c into foo.
6.  the former gdb prompt, do:
-exec-run

Actual results:

The string:

'Missing separate debuginfos, use: debuginfo-install gcc.i386 glib2.i386 glibc.i686 glibmm24.i386 libgtop2.i386 libselinux.i386 libsigc++20.i386 libxml2.i386 zlib.i386'

Appears before the normal GDB/MI formatted messages, normally returned by GDB.


Expected results:

All the messages returned by GDB should be MI compliant, when GDB is using the MI interpreter.

Additional info: