This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug testsuite/13860] Fail in gdb.mi/mi-solib.exp in async mode
- From: "palves at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Tue, 08 May 2012 14:25:05 +0000
- Subject: [Bug testsuite/13860] Fail in gdb.mi/mi-solib.exp in async mode
- Auto-submitted: auto-generated
- References: <bug-13860-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13860
--- Comment #6 from Pedro Alves <palves at redhat dot com> 2012-05-08 14:25:05 UTC ---
I think there's more to it than this.
- -exec-run vs "run" gives different MI output.
- 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
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).
--
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.