qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Bradley Schatz" <blschatz@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] gdbstub breakpoints not working across virtual address spaces
Date: Wed, 19 Sep 2007 22:28:00 +1000	[thread overview]
Message-ID: <a855270a0709190528r5015097av2a9554920791ea9@mail.gmail.com> (raw)

I have breakpoints failing in the case where a breakpoint is set on a
virtual address in another virtual address space. The virtual address
is mapped to nothing in the current virtual address space.

I would like breakpoints to arbitrarily apply across all virtual
address spaces.

My initial investigations suggest that a call to breakpoint_invalidate
after cr3 has been set to the new virtual address space, somewhere in
the softmmu, would be the place to start.

Any suggestions to point me on the right path?

Thanks,

Bradley

             reply	other threads:[~2007-09-19 12:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-19 12:28 Bradley Schatz [this message]
2007-09-19 13:18 ` [Qemu-devel] gdbstub breakpoints not working across virtual address spaces Daniel Jacobowitz
2007-09-19 21:57   ` Bradley Schatz
2007-09-20 23:50     ` Bradley Schatz

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=a855270a0709190528r5015097av2a9554920791ea9@mail.gmail.com \
    --to=blschatz@gmail.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).