mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Andi Kleen <ak@suse.de>
Cc: lkml <linux-kernel@vger.kernel.org>, akpm <akpm@linux-foundation.org>
Subject: [PATCH v3] doc/oops-tracing: add Code: decode info
Date: Fri, 22 Jun 2007 13:28:10 -0700	[thread overview]
Message-ID: <20070622132810.3c758590.randy.dunlap@oracle.com> (raw)
In-Reply-To: <200706221923.02736.ak@suse.de>

From: Randy Dunlap <randy.dunlap@oracle.com>

Add info that the Code: bytes line contains <xy> 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 <randy.dunlap@oracle.com>
---
 Documentation/oops-tracing.txt |   14 ++++++++++++
 scripts/decodecode             |   47 +++++++++++++++++++++++++++++++++++++++++
 2 files changed, 61 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,47 @@
+#!/bin/sh
+# Disassemble the Code: line in Linux oopses
+# usage: decodecode < oops.file
+
+T=`mktemp`
+code=
+
+while read i ; do
+
+case "$i" in
+*Code:*)
+	code=$i
+	;;
+esac
+
+done
+
+if [ -z "$code" ]; then
+	exit
+fi
+
+echo $code
+code=`echo $code | sed -e 's/.*Code: //'`
+
+marker=`expr index "$code" "\<"`
+if [ $marker -eq 0 ]; then
+	marker=`expr index "$code" "\("`
+fi
+
+if [ $marker -ne 0 ]; then
+	beforemark=${code:0:$((marker - 1))}
+	echo -n "	.byte 0x" > $T.s
+	echo $beforemark | sed -e 's/ /,0x/g' >> $T.s
+	as -o $T.o $T.s
+	objdump -S $T.o
+	rm $T.o $T.s
+
+# and fix code at-and-after marker
+	code=${code:$marker}
+fi
+
+code=`echo $code | sed -e 's/ [<(]/ /;s/[>)] / /;s/ /,0x/g'`
+echo -n "	.byte 0x" > $T.s
+echo $code >> $T.s
+as -o $T.o $T.s
+objdump -S $T.o
+rm $T.o $T.s

  parent reply	other threads:[~2007-06-22 20:26 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-22  5:51 [PATCH] " Randy Dunlap
2007-06-22 14:26 ` Andi Kleen
2007-06-22 16:44   ` [PATCH v2] " Randy Dunlap
2007-06-22 17:23     ` Andi Kleen
2007-06-22 18:25       ` Randy Dunlap
2007-06-22 21:29         ` Andi Kleen
2007-06-22 20:28       ` Randy Dunlap [this message]
2007-06-23  8:34         ` NAK (bashizm in the /bin/sh script): [PATCH v3] " Oleg Verych
2007-06-23 11:00           ` Andi Kleen
2007-06-23 11:09             ` Arkadiusz Miskiewicz
2007-06-23 13:17               ` Andi Kleen
2007-06-23 13:26                 ` Willy Tarreau
2007-06-23 13:51                   ` [OT]Re: " Oleg Verych
2007-06-23 13:47                 ` Björn Steinbrink
2007-06-23 14:24                 ` Arkadiusz Miskiewicz
2007-06-23 14:32                 ` Alan Cox
2007-06-23 14:34                   ` Andi Kleen
2007-06-23 14:48                     ` Alan Cox
2007-06-23 15:35                   ` Segher Boessenkool
2007-06-23 14:38                 ` Sean
2007-06-23 15:23                 ` Oleg Verych
2007-06-23 17:43           ` Randy Dunlap
2007-06-23 17:56             ` Andrew Morton
2007-06-23 20:54               ` Adrian Bunk
2007-06-23 21:04                 ` Randy Dunlap
2007-06-23 20:24             ` Matthieu CASTET
2007-06-26 10:16               ` DervishD
2007-06-26 10:24                 ` Jan-Benedict Glaw
2007-06-26 15:33                   ` DervishD
2007-06-26 16:04                     ` Randy Dunlap
2007-06-26 17:03                       ` DervishD
2007-06-26 10:50             ` Arne Georg Gleditsch
2007-06-26 15:36               ` DervishD
2007-06-26 17:19               ` Randy Dunlap
2007-06-26 17:25                 ` Julio M. Merino Vidal
2007-06-26 17:56                   ` Randy Dunlap
2007-06-28  7:58                     ` Arne Georg Gleditsch

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070622132810.3c758590.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®