All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mulyadi Santosa <a_mulyadi@softhome.net>
To: qemu-devel@nongnu.org, Andre Pech <apech@arastra.com>
Subject: Re: [Qemu-devel] Problems with gdbserver and debugging
Date: Thu, 22 Dec 2005 12:31:40 +0700	[thread overview]
Message-ID: <200512221231.40710.a_mulyadi@softhome.net> (raw)
In-Reply-To: <16af12af0512211843h2c73e20v72ec61d150eb13d7@mail.gmail.com>

Hello Andre...

> I'm running into problems using qemu to debug a kernel module. My
> host and virtual machine are both x86 running Fedora Core 4. After
> insmoding the module in the virtual machine, starting gdbserver,
> running gdb on the host with the module sections loaded at the right
> place, and setting a breakpoint in the module code, gdb does not
> always get notified when the code is exectuted. After adding

I'm not doing module debugging, only core kernel code debugging, but 
more or less I run into same situation (last time confirmed with Qemu 
0.7.1)

For additional info, sometimes I also suffered the other condition. 
Breakpoint is hit, but even if I delete it, the emulation still stops 
whenever the code at related physical address is hit. I tried to 
printf() every gdb command received by Qemu's gdbstub and it confirmed 
that breakpoint deletion command is actually received, but I can't 
confirm what is the real bug there.

regards

Mulyadi

      parent reply	other threads:[~2005-12-22  5:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-22  2:43 [Qemu-devel] Problems with gdbserver and debugging Andre Pech
2005-12-22  5:16 ` Tace
2005-12-22  5:31 ` Mulyadi Santosa [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=200512221231.40710.a_mulyadi@softhome.net \
    --to=a_mulyadi@softhome.net \
    --cc=apech@arastra.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.