Re: [PATCH v2] doc/oops-tracing: add Code: decode info

[Andi Kleen <ak@suse.de>]

On Friday 22 June 2007 18:44, Randy Dunlap wrote:
> 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 <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 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 <xy> or (wxyz)
> > > markings.)
> >
> > Should probably fix that and put it into scripts/ then
>
> From: Randy Dunlap <randy.dunlap@oracle.com>

Thanks.

>
> +*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

This still has a couple of problems:

- The <> information is lost. It would be better to split and run 
objdump three times and insert a marker
- It won't handle multiline Code:s which i386 likes to generate now I think

-Andi