This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/13860] Different sync vs async MI output
- From: "palves at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Thu, 22 May 2014 10:54:30 +0000
- Subject: [Bug gdb/13860] Different sync vs async MI output
- Auto-submitted: auto-generated
- References: <bug-13860-4717 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=13860
Pedro Alves <palves at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |---
Summary|Fail in gdb.mi/mi-solib.exp |Different sync vs async MI
|in async mode |output
--- Comment #14 from Pedro Alves <palves at redhat dot com> ---
Oh, I forgot, there's more. From mi-cli.exp:
# When a CLI command is entered in MI session, the respose is different in
# sync and async modes. In sync mode normal_stop is called when current
# interpreter is CLI. So:
# - print_stop_reason prints stop reason in CLI uiout, and we don't show it
# in MI
# - The stop position is printed, and appears in MI 'console' channel.
#
# In async mode the stop event is processed when we're back to MI interpreter,
# so the stop reason is printed into MI uiout an.
if {$async} {
set reason "end-stepping-range"
} else {
set reason ""
}
mi_execute_to "interpreter-exec console step" $reason "callee4" "" ".*basics.c"
$line_callee4_next \
and:
# Note that the output does not include stop reason. This is fine.
# The purpose of *stopped notification for CLI command is to make
# sure that frontend knows that inferior is stopped, and knows where.
# Supplementary information is not necessary.
mi_expect_stop "end-stepping-range" "main" "" ".*basics.c" $line_main_return ""
\
--
You are receiving this mail because:
You are on the CC list for the bug.