From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JyrjG-0006uZ-Sz for qemu-devel@nongnu.org; Wed, 21 May 2008 13:03:54 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JyrjE-0006t0-JC for qemu-devel@nongnu.org; Wed, 21 May 2008 13:03:53 -0400 Received: from [199.232.76.173] (port=52292 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JyrjE-0006su-4d for qemu-devel@nongnu.org; Wed, 21 May 2008 13:03:52 -0400 Received: from mail.windriver.com ([147.11.1.11]:41670 helo=mail.wrs.com) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JyrjD-00056N-Hq for qemu-devel@nongnu.org; Wed, 21 May 2008 13:03:52 -0400 Received: from ALA-MAIL03.corp.ad.wrs.com (ala-mail03 [147.11.57.144]) by mail.wrs.com (8.13.6/8.13.6) with ESMTP id m4LH3jQt026859 for ; Wed, 21 May 2008 10:03:46 -0700 (PDT) Message-ID: <483455E3.1080706@windriver.com> Date: Wed, 21 May 2008 12:03:31 -0500 From: Jason Wessel MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH 2/5] gdbstub: gdb pass-through qemu monitor support References: <1210860693-22245-1-git-send-email-jason.wessel@windriver.com> <1210860693-22245-2-git-send-email-jason.wessel@windriver.com> <1210860693-22245-3-git-send-email-jason.wessel@windriver.com> <20080515221716.GC27300@edgar.se.axis.com> <483180AD.40704@windriver.com> <291f35090805210558l3eae915ch5937c311f37f91bd@mail.gmail.com> In-Reply-To: <291f35090805210558l3eae915ch5937c311f37f91bd@mail.gmail.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Maxim Gorbachyov wrote: > On Mon, May 19, 2008 at 5:29 PM, Jason Wessel > wrote: > > [cut] > >> Seems reasonable too, see newly attached patch. >> >> Obviously you need the new monitor patch applied prior to this one. >> This patch was updated against the prior patch. >> > > It was noticed [by Jan Kiszka and me] that the output on the monitor > console goes both to the local as well as the remote one - but only if > you issue a command via gdb. When you type in the command locally (ie. > on the qemu side), that output is not forwarded to the gdb frontend. > Is this behavior desired? > > > That was certainly the intended behavior when I created the patch. There is no reason to feed the monitor output up to the debugger that may or may not be attached. The behavior could get altered to check if the debugger is in the "continue" state and then send the information from the monitor, but it seemed of little value to do so. Jason.