From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kip Macy Subject: Re: Reproducible system crash Date: Wed, 16 Mar 2005 11:35:46 -0800 Message-ID: References: <240b7ae935630db1625e232e965650a4@cl.cam.ac.uk> Reply-To: Kip Macy Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit In-Reply-To: <240b7ae935630db1625e232e965650a4@cl.cam.ac.uk> Sender: xen-devel-admin@lists.sourceforge.net Errors-To: xen-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: xen-devel@lists.sourceforge.net, Peter Joanes List-Id: xen-devel@lists.xenproject.org Real men don't use debuggers ;-) but for those of us who do: gdb vmlinux (gdb) x/i 0xc01099a will do the same thing. If you have symbols compiled in, you can also do : (gdb) info line *0xc01099a and get the exact line of C code. -Kip > The stack backtrace also indicates that the code at address 0xc010990a > in XenLinux may also be interesting (that is the code point that caused > the crash). > 'objdump -d vmlinux' and then grep the output for that address.... > ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click