From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1IYVnG-0003RI-SQ
	for qemu-devel@nongnu.org; Thu, 20 Sep 2007 19:50:50 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1IYVnF-0003Qu-BN
	for qemu-devel@nongnu.org; Thu, 20 Sep 2007 19:50:50 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1IYVnF-0003Qk-80
	for qemu-devel@nongnu.org; Thu, 20 Sep 2007 19:50:49 -0400
Received: from wa-out-1112.google.com ([209.85.146.180])
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <blschatz@gmail.com>) id 1IYVnE-00075s-RJ
	for qemu-devel@nongnu.org; Thu, 20 Sep 2007 19:50:49 -0400
Received: by wa-out-1112.google.com with SMTP id k22so860345waf
	for <qemu-devel@nongnu.org>; Thu, 20 Sep 2007 16:50:47 -0700 (PDT)
Message-ID: <a855270a0709201650vc228d51q3f8300532a5c8d8c@mail.gmail.com>
Date: Fri, 21 Sep 2007 09:50:46 +1000
From: "Bradley Schatz" <blschatz@gmail.com>
Subject: Re: [Qemu-devel] gdbstub breakpoints not working across virtual
	address spaces
In-Reply-To: <a855270a0709191457k2d82017fja6487287a852508e@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <a855270a0709190528r5015097av2a9554920791ea9@mail.gmail.com>
	<20070919131821.GA29275@caradoc.them.org>
	<a855270a0709191457k2d82017fja6487287a852508e@mail.gmail.com>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

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
> >
> >
> >
>