From: Jason Wessel <jason.wessel@windriver.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Debugging vmlinux with qemu and gdb. Unable to step, next, print or to get any information..
Date: Fri, 09 May 2008 09:47:19 -0500 [thread overview]
Message-ID: <482463F7.3050407@windriver.com> (raw)
In-Reply-To: <20080509144029.GA32414@caradoc.them.org>
Daniel Jacobowitz wrote:
> On Thu, May 08, 2008 at 11:39:11PM -0500, Jason Wessel wrote:
>
>> +@item maintenance packet qqemu.sstepbits
>>
>
> Are these packets in wide use yet? If not, I'd really recommend you
> use qRcmd instead; then the GDB command is just "monitor", e.g.
> "monitor show sstepbits". maint packet isn't really intended for
> users.
>
>
I highly doubt there is any kind of wide spread use here. This is qemu
specific and at that, it is really low level.
Because you mentioned it though I'll have a look. I seem to recall there
was some kind of encoding for monitor packets which should be straight
forward enough.
Thanks,
Jason.
next prev parent reply other threads:[~2008-05-09 14:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-08 7:53 [Qemu-devel] Debugging vmlinux with qemu and gdb. Unable to step, next, print or to get any information Keilhau Timo ( Student )
2008-05-08 8:28 ` [Qemu-devel] " Jan Kiszka
2008-05-08 9:09 ` Keilhau Timo ( Student )
2008-05-08 18:39 ` Jan Kiszka
2008-05-09 2:31 ` [Qemu-devel] " Mulyadi Santosa
2008-05-09 4:39 ` Jason Wessel
2008-05-09 7:23 ` Mulyadi Santosa
2008-05-09 8:29 ` Jan Kiszka
2008-05-09 9:03 ` Keilhau Timo ( Student )
2008-05-09 10:03 ` Mulyadi Santosa
2008-05-09 8:38 ` Edgar E. Iglesias
2008-05-09 14:40 ` Daniel Jacobowitz
2008-05-09 14:47 ` Jason Wessel [this message]
2008-05-09 16:39 ` Daniel Jacobowitz
2008-05-12 9:41 ` Edgar E. Iglesias
2008-05-12 12:51 ` Jason Wessel
2008-05-12 13:30 ` Edgar E. Iglesias
2008-05-12 14:02 ` Edgar E. Iglesias
2008-05-12 14:31 ` Jason Wessel
2008-05-12 14:33 ` Paul Brook
2008-05-12 14:47 ` Edgar E. Iglesias
2008-05-12 14:48 ` Jason Wessel
2008-05-12 12:51 ` Daniel Jacobowitz
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=482463F7.3050407@windriver.com \
--to=jason.wessel@windriver.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.