qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Bradley Schatz" <blschatz@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] gdbstub breakpoints not working across virtual address spaces
Date: Fri, 21 Sep 2007 09:50:46 +1000	[thread overview]
Message-ID: <a855270a0709201650vc228d51q3f8300532a5c8d8c@mail.gmail.com> (raw)
In-Reply-To: <a855270a0709191457k2d82017fja6487287a852508e@mail.gmail.com>

Trying things a different way, I find that issuing a:
  breakpoint *0xc...

will break properly.


On 9/20/07, Bradley Schatz <blschatz@gmail.com> wrote:
> I am running a windows2k guest, which in turn is running coLinux. I
> wish to set a breakpoint in the linux instance.
>
> A windows driver loads, and builds the page tables of two independent
> virtual address spaces, and backs them with page frames allocated
> using the windows driver API. The two addreess spaces are a trampoline
> address space, and then the coLinux address space. The driver then
> switches to the linux virtual address space via the trampoline space.
>
> I am currently setting a breakpoint on an address in the linux address
> space before the driver is even loaded. On running, the breakpoint is
> ignored, but colinux runs.
>
> Thanks,
>
> Bradley
>
>
>
> On 9/19/07, Daniel Jacobowitz <drow@false.org> wrote:
> > On Wed, Sep 19, 2007 at 10:28:00PM +1000, Bradley Schatz wrote:
> > > 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.
> >
> > I think they already do.  Specific example, please.
> >
> > --
> > Daniel Jacobowitz
> > CodeSourcery
> >
> >
> >
>

      reply	other threads:[~2007-09-20 23:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-19 12:28 [Qemu-devel] gdbstub breakpoints not working across virtual address spaces Bradley Schatz
2007-09-19 13:18 ` Daniel Jacobowitz
2007-09-19 21:57   ` Bradley Schatz
2007-09-20 23:50     ` Bradley Schatz [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=a855270a0709201650vc228d51q3f8300532a5c8d8c@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).