From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IXyf0-0001y6-J3 for qemu-devel@nongnu.org; Wed, 19 Sep 2007 08:28:06 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IXyex-0001vH-ND for qemu-devel@nongnu.org; Wed, 19 Sep 2007 08:28:06 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IXyex-0001v3-Gg for qemu-devel@nongnu.org; Wed, 19 Sep 2007 08:28:03 -0400 Received: from wa-out-1112.google.com ([209.85.146.182]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IXyex-0003jO-7J for qemu-devel@nongnu.org; Wed, 19 Sep 2007 08:28:03 -0400 Received: by wa-out-1112.google.com with SMTP id k22so237564waf for ; Wed, 19 Sep 2007 05:28:01 -0700 (PDT) Message-ID: Date: Wed, 19 Sep 2007 22:28:00 +1000 From: "Bradley Schatz" MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: [Qemu-devel] gdbstub breakpoints not working across virtual address spaces Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org 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