Hello,

With the mi2 interpreter, when one issues a break command
(either '-break-insert <classname::function-name>' or the cli
'break <classname::function-name>' command)
in the context of a C++ inferior, an overloaded
function resolution can happen.

In that case, the breakpoint setting code
asks the user to choose the overloaded function it wants to break in.
To do so, the breakpoint setting code displays something like:

~"[0] cancel\n[1] all\n"
~"[2] classname::function_name(int) at fooprog.cc:65\n"
~"[3] classname::function_name() at fooprog.cc:59\n"
~"> "

The last line of this "question" is the default prompt indicating the end
of the question.

In gdb 6.7.1, that prompt is missing *only* when using the MI interpreter.
It is present in the CLI interpreter. And this is a regression from 6.6
where the prompt was present with both interpreters.

The prompt is really important for graphical front-end tools willing
to parse that "question" so that they can display display it
back to the user in a nice windowed manner.
As the question does not really respect the GDB/MI output format where the
output should be ended by a "(gdb)" string, the prompt is the only way th
front end can detect the end of the "question".

So I tried to produce the attached patch to pinpoint the problem and hopefully
propose a fix.

Cheers,

-- 
Dodji Seketeli
http://www.seketeli.org/dodji