From: Daniel Jacobowitz <drow@false.org>
To: "Edgar E. Iglesias" <edgar.iglesias@axis.com>
Cc: 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: Mon, 12 May 2008 08:51:35 -0400 [thread overview]
Message-ID: <20080512125135.GA30870@caradoc.them.org> (raw)
In-Reply-To: <20080512094103.GA31632@edgar.se.axis.com>
On Mon, May 12, 2008 at 11:41:03AM +0200, Edgar E. Iglesias wrote:
> Thanks for the comments Daniel.
>
> This patch tries to change the syntax into this:
> % monitor sstepbits
> % monitor sstep
> % monitor sstep=0x05
>
> Or would a show/set interface be prefered for some reason (e.g,
> monitor show sstepbits, monitor show sstep, monitor set sstep 0x5)?
The only reason I suggested set/show is that that's how the GDB
command line works. I think the important part is using monitor
rather than custom packets; the set style is just sugar.
Thanks!
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2008-05-12 12:51 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
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 [this message]
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=20080512125135.GA30870@caradoc.them.org \
--to=drow@false.org \
--cc=edgar.iglesias@axis.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.