From mboxrd@z Thu Jan 1 00:00:00 1970 From: Razvan Cojocaru Subject: Re: Mem_event API and MEM_EVENT_REASON_SINGLESTEP Date: Fri, 30 Nov 2012 23:14:08 +0200 Message-ID: <50B921A0.5020205@gmail.com> References: <50B77375.9070904@gmail.com> <50B77CB8.1040606@gmail.com> <50B91273.6050606@gmail.com> <20121130210708.GA2013@ocelot.phlegethon.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20121130210708.GA2013@ocelot.phlegethon.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Tim Deegan Cc: jepstein98@gmail.com, "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org > What more do you want to know? The gla tells you what the address is > that's being written to. If you want the rest of the register state &c, > then have a look at either tools/debugger/gdbsx (a full debugger stub > for guests; its maintainer is Mukesh Rathor ) > or tools/xentrace/xenctx.c (which has some code to print registers, read > memory addresses, &c) Excellent. Will look those up. Thanks, Razvan