From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rusty Russell Subject: Re: [PATCH] Lguest32 print hex on bad reads and writes Date: Thu, 05 Apr 2007 13:34:17 +1000 Message-ID: <1175744057.12230.632.camel@localhost.localdomain> References: <1175714071.9371.31.camel@localhost.localdomain> <1175742090.12230.630.camel@localhost.localdomain> <72C854B9-1A7F-44C5-9D62-B6B63F3A6DE7@mac.com> <1175742848.9371.33.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <1175742848.9371.33.camel@localhost.localdomain> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: virtualization-bounces@lists.linux-foundation.org Errors-To: virtualization-bounces@lists.linux-foundation.org To: Steven Rostedt Cc: virtualization@lists.osdl.org, Linux Kernel Mailing List , Kyle Moffett List-Id: virtualization@lists.linuxfoundation.org On Wed, 2007-04-04 at 23:14 -0400, Steven Rostedt wrote: > On Wed, 2007-04-04 at 23:06 -0400, Kyle Moffett wrote: > = > > > (Erk, I wonder what I was thinking when I wrote that?) Can I ask = > > > for %#x (or 0x%x)? I'm easily confused. > > = > > How about "%p" for pointers? > = > But that would require casting the numbers to pointers. And the kernel's printk doesn't put 0x on pointers anyway, last I checked 8( Rusty.