qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jun Koi <junkoi2004@gmail.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: Problem with watchpoint in gdbstub
Date: Tue, 27 Apr 2010 18:12:33 +0900	[thread overview]
Message-ID: <p2zfdaac4d51004270212t850d5be1q2fa3447be215209d@mail.gmail.com> (raw)
In-Reply-To: <4BD69C10.50606@siemens.com>

On Tue, Apr 27, 2010 at 5:10 PM, Jan Kiszka <jan.kiszka@siemens.com> wrote:
> Jun Koi wrote:
>> Hi,
>>
>> I am trying to debug a VM using gdb. I connected gdb to Qemu (latest
>> code from git repo), and issued below command:
>>
>> ...
>> (gdb) watch *0x77f44cd8
>> (gdb) c
>>
>> The idea is to catch the write access to address 0x77f44cd8.
>>
>> But after the "c" command, I saw that the window title of my VM
>> continuously flip between "QEMU [Stopped]" and "QEMU", non-stop.
>> This makes the VM unusable.
>>
>> Is it a bug? Anybody sees the same problem?
>
> I would bet your watchpoint was established by gdb as a software
> watchpoint. In that case gdb will step through the target, checking
> after each instruction if the memory changed.

But that is certainly not the reason of the symptom I saw.


>
> Is that address valid at the time gdb wants to install it? I saw gdb
> choosing a software watchpoint before when it wasn't.

Yes, that address is valid.

thanks,
J

  reply	other threads:[~2010-04-27  9:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-26  5:31 [Qemu-devel] Problem with watchpoint in gdbstub Jun Koi
2010-04-27  8:10 ` [Qemu-devel] " Jan Kiszka
2010-04-27  9:12   ` Jun Koi [this message]
2010-04-27  9:30     ` Jan Kiszka
2010-04-27  9:40       ` Jun Koi
2010-04-27 10:22         ` Jan Kiszka

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=p2zfdaac4d51004270212t850d5be1q2fa3447be215209d@mail.gmail.com \
    --to=junkoi2004@gmail.com \
    --cc=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 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).