From: Jan Kiszka <jan.kiszka@web.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH 2/5] gdbstub: gdb pass-through qemu monitor support
Date: Thu, 22 May 2008 15:53:06 +0200 [thread overview]
Message-ID: <48357AC2.5010302@web.de> (raw)
In-Reply-To: <483578EB.1070403@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 2133 bytes --]
Jason Wessel wrote:
> Jan Kiszka wrote:
>> Jason Wessel wrote:
>>
>>> Maxim Gorbachyov wrote:
>>>
>>>> On Mon, May 19, 2008 at 5:29 PM, Jason Wessel
>>>> <jason.wessel@windriver.com> 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.
>>>
>> That's not what we were confused by.
>>
>>
>>> 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.
>>>
>> Rather the contrary: What is the point of mirroring the output you see
>> in gdb to the local monitor console?
>>
>>
>
> That happens to have little to do with the gdb implementation. It is a
> function of the monitor mux. The monitor mux always writes out to all
> the output channels automatically. In the case of gdb sending input
> for which you only want to receive the response it would be plausible to
> add a "focus" parameter to the monitor mux code to indicate which
> "channel" to send the output to.
>
> The monitor mux could also be changed to simply shift the output focus
> to the most recent place it received an input, and if the focus was -1
> to start it would broadcast every where, the way it does today. It is a
> trivial enough change, if this is what you are looking for.
Yep, would be nice.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 254 bytes --]
next prev parent reply other threads:[~2008-05-22 13:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-15 14:11 [Qemu-devel] [PATCH 0/5] gdbstub and single step improvments Jason Wessel
2008-05-15 14:11 ` [Qemu-devel] [PATCH 1/5] gdbstub: replace singlestep q packets with qRcmd packets Jason Wessel
2008-05-15 14:11 ` [Qemu-devel] [PATCH 2/5] gdbstub: gdb pass-through qemu monitor support Jason Wessel
2008-05-15 14:11 ` [Qemu-devel] [PATCH 3/5] vl.c: always run the real time timers when single stepping Jason Wessel
2008-05-15 14:11 ` [Qemu-devel] [PATCH 4/5] gdbstub: support for gdb "detach/kill/quit" Jason Wessel
2008-05-15 14:11 ` [Qemu-devel] [PATCH 5/5] ppc: fix crash in ppc system single step support Jason Wessel
2008-05-15 21:13 ` [Qemu-devel] [PATCH 4/5] gdbstub: support for gdb "detach/kill/quit" Edgar E. Iglesias
2008-05-15 22:17 ` [Qemu-devel] [PATCH 2/5] gdbstub: gdb pass-through qemu monitor support Edgar E. Iglesias
2008-05-19 13:29 ` Jason Wessel
2008-05-19 16:30 ` Paul Brook
2008-05-21 12:58 ` Maxim Gorbachyov
2008-05-21 17:03 ` Jason Wessel
2008-05-22 13:24 ` [Qemu-devel] " Jan Kiszka
2008-05-22 13:45 ` Jason Wessel
2008-05-22 13:53 ` Jan Kiszka [this message]
2008-05-22 16:55 ` Jason Wessel
2008-05-23 15:33 ` Jan Kiszka
2008-05-15 21:33 ` [Qemu-devel] [PATCH 1/5] gdbstub: replace singlestep q packets with qRcmd packets Edgar E. Iglesias
2008-05-19 13:27 ` Jason Wessel
2008-05-19 15:14 ` Edgar E. Iglesias
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48357AC2.5010302@web.de \
--to=jan.kiszka@web.de \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).