Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759526AbXFVQnN (ORCPT ); Fri, 22 Jun 2007 12:43:13 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758537AbXFVQmu (ORCPT ); Fri, 22 Jun 2007 12:42:50 -0400 Received: from rgminet01.oracle.com ([148.87.113.118]:16526 "EHLO rgminet01.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758293AbXFVQmt (ORCPT ); Fri, 22 Jun 2007 12:42:49 -0400 Date: Fri, 22 Jun 2007 09:44:29 -0700 From: Randy Dunlap To: Andi Kleen Cc: lkml , akpm Subject: [PATCH v2] doc/oops-tracing: add Code: decode info Message-Id: <20070622094429.0910c7cb.randy.dunlap@oracle.com> In-Reply-To: <200706221626.39969.ak@suse.de> References: <20070621225108.bb69a93d.randy.dunlap@oracle.com> <200706221626.39969.ak@suse.de> Organization: Oracle Linux Eng. X-Mailer: Sylpheed 2.4.2 (GTK+ 2.8.10; x86_64-unknown-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Brightmail-Tracker: AAAAAQAAAAI= X-Brightmail-Tracker: AAAAAQAAAAI= X-Whitelist: TRUE X-Whitelist: TRUE Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2849 Lines: 82 On Fri, 22 Jun 2007 16:26:39 +0200 Andi Kleen wrote: > On Friday 22 June 2007 07:51:08 Randy Dunlap wrote: > > From: Randy Dunlap > > > > Add info that the Code: bytes line contains or (wxyz) in some > > architecture oops reports and what that means. > > > > Add URL for a script by Andi Kleen that reads the Code: line from an Oops > > report file and generates assembly code from the hex bytes. > > (This script does not handle Code: lines that contain or (wxyz) > > markings.) > > Should probably fix that and put it into scripts/ then From: Randy Dunlap Add info that the Code: bytes line contains or (wxyz) in some architecture oops reports and what that means. Add a script by Andi Kleen that reads the Code: line from an Oops report file and generates assembly code from the hex bytes. Signed-off-by: Randy Dunlap --- Documentation/oops-tracing.txt | 14 ++++++++++++++ scripts/decodecode | 20 ++++++++++++++++++++ 2 files changed, 34 insertions(+) --- linux-2.6.22-rc5.orig/Documentation/oops-tracing.txt +++ linux-2.6.22-rc5/Documentation/oops-tracing.txt @@ -86,6 +86,20 @@ stuff are the values reported by the Oop and do a replace of spaces to "\x" - that's what I do, as I'm too lazy to write a program to automate this all). +Alternatively, you can use the shell script in scripts/decodecode. +Its usage is: decodecode < oops.txt + +The hex bytes that follow "Code:" may (in some architectures) have a series +of bytes that precede the current instruction pointer as well as bytes at and +following the current instruction pointer. In some cases, one instruction +byte or word is surrounded by <> or (), as in "<86>" or "(f00d)". These +<> or () markings indicate the current instruction pointer. Example from +i386, split into multiple lines for readability: + +Code: f9 0f 8d f9 00 00 00 8d 42 0c e8 dd 26 11 c7 a1 60 ea 2b f9 8b 50 08 a1 +64 ea 2b f9 8d 34 82 8b 1e 85 db 74 6d 8b 15 60 ea 2b f9 <8b> 43 04 39 42 54 +7e 04 40 89 42 54 8b 43 04 3b 05 00 f6 52 c0 + Finally, if you want to see where the code comes from, you can do cd /usr/src/linux --- /dev/null +++ linux-2.6.22-rc5/scripts/decodecode @@ -0,0 +1,20 @@ +#!/bin/sh +# Disassemble the Code: line in Linux oopses +# usage: decodecode < oops.file + +T=`mktemp` + +while read i ; do + +case "$i" in +*Code:*) + echo $i + echo -n " .byte 0x" > $T.s + echo $i | sed -e 's/.*Code: //;s/ [<(]/ /;s/[>)] / /;s/ /,0x/g' >> $T.s + as -o $T.o $T.s + objdump -S $T.o + rm $T.o $T.s + ;; +esac + +done - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/