qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wessel <jason.wessel@windriver.com>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org, "Edgar E. Iglesias" <edgar.iglesias@axis.com>
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 09:48:47 -0500	[thread overview]
Message-ID: <482858CF.6030408@windriver.com> (raw)
In-Reply-To: <200805121533.32363.paul@codesourcery.com>

Paul Brook wrote:
>> Btw, while your at it you might want to consider another comment. When
>> trying the sstep I felt it was easy to get confused with the negated
>> bitmasks. Maybe we should invert them?
>>
>> The default bitmask would change to 1. And sstepbits would be
>> "ENABLE=1,IRQ=2,TIMERS=4". Does that make sense?
>>     
>
> Or just have the command use symbolic names rather than numeric values.
>
> Paul
>   
In terms of the user interface, it looks like:

(gdb) monitor help
gdbstub specific monitor commands:
s_show -- Show gdbstub Single Stepping variables
set s_step <0|1> -- Single Stepping enabled
set s_irq <0|1> -- Single Stepping with qemu irq handlers enabled
set s_timer <0|1> -- Single Stepping with qemu timers enabled
qemu monitor pass-through commands:
help|? [cmd] -- show the help
commit device|all -- commit changes to the disk images (if -snapshot is
used) or backing files
info subcommand -- show various information about the system state
q|quit -- quit the emulator
[...clip... normal qemu monitor stuff]

(gdb) monitor s_show
s_step == 1
s_irq == 0
s_timer == 0

The implementation of the internals with the #defines did not change in
any fundamental way. The patches for this will be posted after further
testing in the next day or so for further comments. Also the timers
option is probably going to go away entirely.

Jason.

  parent reply	other threads:[~2008-05-12 14:49 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 [this message]
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=482858CF.6030408@windriver.com \
    --to=jason.wessel@windriver.com \
    --cc=edgar.iglesias@axis.com \
    --cc=paul@codesourcery.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 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).