[Bug testsuite/13860] Fail in gdb.mi/mi-solib.exp in async mode

["qiyao at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>]

http://sourceware.org/bugzilla/show_bug.cgi?id=13860

--- Comment #8 from Yao Qi <qiyao at gcc dot gnu.org> 2012-05-09 08:03:52 UTC ---
(In reply to comment #7)
> (In reply to comment #6)
> > I think there's more to it than this.
> > 
> > - -exec-run vs "run" gives different MI output.
> > 
> 
> Oh, I didn't notice this.
> 
> > - The ~"Stopped due to shared library event (no libraries added or removed)\n"
> >   bit is not output in async, when the user issues a CLI command.  Or more
> 
> Yes, I find this line doesn't exits in async gdb.log.
> 
> > generally, CLI execution commands don't produce output when the command
> > finishes in async mode (e.g., "next").  I think they should, for the benefit of
> > the user doing commands in the gdb console of a frontend (such as Eclipse).
> 
> That sounds like a serious problem, IMO.  I agree with you that command output
> should be produced, no matter which mode (sync vs. async) gdb is running on.
> 
> Existing mi test cases don't check much about CLI output, which should be
> improved.

My patch posted in comment#5 fixes this fail, but causes some regressions in
both sync mode and async mode,

-PASS: gdb.mi/mi2-simplerun.exp: exec-finish
+FAIL: gdb.mi/mi2-simplerun.exp: exec-finish (unknown output after running)
-PASS: gdb.mi/mi-simplerun.exp: exec-finish
+FAIL: gdb.mi/mi-simplerun.exp: exec-finish (unknown output after running)

They are about the two points you mentioned in comment#6.  You looked far ahead
a little bit :)

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.