From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-prs-return-15763-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Received: (qmail 31822 invoked by alias); 22 May 2014 10:54:34 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Received: (qmail 31785 invoked by uid 48); 22 May 2014 10:54:32 -0000
From: "palves at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/13860] Different sync vs async MI output
Date: Thu, 22 May 2014 10:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: gdb
X-Bugzilla-Version: HEAD
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: palves at redhat dot com
X-Bugzilla-Status: REOPENED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: palves at redhat dot com
X-Bugzilla-Target-Milestone: 7.8
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution short_desc
Message-ID: <bug-13860-4717-ECoeKSNXwn@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-13860-4717@http.sourceware.org/bugzilla/>
References: <bug-13860-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-q2/txt/msg00269.txt.bz2

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.