diff options
| -rw-r--r-- | Documentation/oops-tracing.txt | 14 | ||||
| -rw-r--r-- | scripts/decodecode | 51 |
2 files changed, 65 insertions, 0 deletions
diff --git a/Documentation/oops-tracing.txt b/Documentation/oops-tracing.txt index 7d5b60dea551..23e6dde7eea6 100644 --- a/Documentation/oops-tracing.txt +++ b/Documentation/oops-tracing.txt | |||
| @@ -86,6 +86,20 @@ stuff are the values reported by the Oops - you can just cut-and-paste | |||
| 86 | and do a replace of spaces to "\x" - that's what I do, as I'm too lazy | 86 | and do a replace of spaces to "\x" - that's what I do, as I'm too lazy |
| 87 | to write a program to automate this all). | 87 | to write a program to automate this all). |
| 88 | 88 | ||
| 89 | Alternatively, you can use the shell script in scripts/decodecode. | ||
| 90 | Its usage is: decodecode < oops.txt | ||
| 91 | |||
| 92 | The hex bytes that follow "Code:" may (in some architectures) have a series | ||
| 93 | of bytes that precede the current instruction pointer as well as bytes at and | ||
| 94 | following the current instruction pointer. In some cases, one instruction | ||
| 95 | byte or word is surrounded by <> or (), as in "<86>" or "(f00d)". These | ||
| 96 | <> or () markings indicate the current instruction pointer. Example from | ||
| 97 | i386, split into multiple lines for readability: | ||
| 98 | |||
| 99 | 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 | ||
| 100 | 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 | ||
| 101 | 7e 04 40 89 42 54 8b 43 04 3b 05 00 f6 52 c0 | ||
| 102 | |||
| 89 | Finally, if you want to see where the code comes from, you can do | 103 | Finally, if you want to see where the code comes from, you can do |
| 90 | 104 | ||
| 91 | cd /usr/src/linux | 105 | cd /usr/src/linux |
diff --git a/scripts/decodecode b/scripts/decodecode new file mode 100644 index 000000000000..1e1a8f620c47 --- /dev/null +++ b/scripts/decodecode | |||
| @@ -0,0 +1,51 @@ | |||
| 1 | #!/bin/sh | ||
| 2 | # Disassemble the Code: line in Linux oopses | ||
| 3 | # usage: decodecode < oops.file | ||
| 4 | # | ||
| 5 | # options: set env. variable AFLAGS=options to pass options to "as"; | ||
| 6 | # e.g., to decode an i386 oops on an x86_64 system, use: | ||
| 7 | # AFLAGS=--32 decodecode < 386.oops | ||
| 8 | |||
| 9 | T=`mktemp` | ||
| 10 | code= | ||
| 11 | |||
| 12 | while read i ; do | ||
| 13 | |||
| 14 | case "$i" in | ||
| 15 | *Code:*) | ||
| 16 | code=$i | ||
| 17 | ;; | ||
| 18 | esac | ||
| 19 | |||
| 20 | done | ||
| 21 | |||
| 22 | if [ -z "$code" ]; then | ||
| 23 | exit | ||
| 24 | fi | ||
| 25 | |||
| 26 | echo $code | ||
| 27 | code=`echo $code | sed -e 's/.*Code: //'` | ||
| 28 | |||
| 29 | marker=`expr index "$code" "\<"` | ||
| 30 | if [ $marker -eq 0 ]; then | ||
| 31 | marker=`expr index "$code" "\("` | ||
| 32 | fi | ||
| 33 | |||
| 34 | if [ $marker -ne 0 ]; then | ||
| 35 | beforemark=`echo "$code" | cut -c-$((${marker} - 1))` | ||
| 36 | echo -n " .byte 0x" > $T.s | ||
| 37 | echo $beforemark | sed -e 's/ /,0x/g' >> $T.s | ||
| 38 | as $AFLAGS -o $T.o $T.s | ||
| 39 | objdump -S $T.o | ||
| 40 | rm $T.o $T.s | ||
| 41 | |||
| 42 | # and fix code at-and-after marker | ||
| 43 | code=`echo "$code" | cut -c$((${marker} + 1))-` | ||
| 44 | fi | ||
| 45 | |||
| 46 | code=`echo $code | sed -e 's/ [<(]/ /;s/[>)] / /;s/ /,0x/g'` | ||
| 47 | echo -n " .byte 0x" > $T.s | ||
| 48 | echo $code >> $T.s | ||
| 49 | as $AFLAGS -o $T.o $T.s | ||
| 50 | objdump -S $T.o | ||
| 51 | rm $T.o $T.s | ||
