All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.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 10:29:02 +0200	[thread overview]
Message-ID: <48240B4E.2060309@siemens.com> (raw)
In-Reply-To: <f284c33d0805090023v582f45b4gf85cd672f19e47f2@mail.gmail.com>

Mulyadi Santosa wrote:
> HI Jason...
> 
> On Fri, May 9, 2008 at 11:39 AM, Jason Wessel
> <jason.wessel@windriver.com> wrote:
>>> Of course, this assume that there is no bugs while Qemu inspect and
>>> found that it must pause at certain address... I believe Jasson Wessel
>>> had squashed all that kind of bugs in the past.
>>>
>>> regards,
>>>
>>> Mulyadi.
>>>
>>>
>> I believe that Mulyadi is talking about the following two patches which
>> are attached here, assuming you are able to hit breakpoints.
> 
> Thanks.... I believe that's the patch that will fix his problem.

I'm not /that/ sure. The second one affects single stepping only, and
the first one is now redundant as QEMU (and thus also KVM) uses a
compacter way of supporting x86-64 registers. But maybe the patch is
still required for "old" QEMU 0.9.1 (I'm working with development heads
only). But IIRC, the error pattern used to be quite different when QEMU
did not yet support x86-64 registers.

Jan

-- 
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux

  reply	other threads:[~2008-05-09  8:29 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 [this message]
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

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=48240B4E.2060309@siemens.com \
    --to=jan.kiszka@siemens.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.