04 Jun, 2010

1 commit


02 Feb, 2010

1 commit

  • This patch adds support for decoding ARM oopses to scripts/decodecode.
    The following things are handled:

    - ARCH and CROSS_COMPILE environment variables are respected.

    - The Code: in x86 oopses is in bytes, while it is in either words (4
    bytes) or halfwords for ARM.

    - Some versions of ARM objdump refuse to disassemble instructions
    generated by literal constants (".word 0x..."). The workaround is to
    strip the object file first.

    - The faulting instruction is marked (liked so) in ARM, but
    in x86.

    - ARM mnemonics may include characters such as [] which need to be
    escaped before being passed to sed for the "
    Signed-off-by: Michal Marek

    Rabin Vincent
     

04 Dec, 2008

1 commit

  • kerneloops.org has been using an improved "decodecode" script,
    specifically it has a special marker that shows which line in the assembly
    the oops happened at, like this:

    20: 83 e0 03 and $0x3,%eax
    23: 09 d8 or %ebx,%eax
    25: 85 db test %ebx,%ebx
    27: 89 02 mov %eax,(%edx)
    29: 74 0f je 0x3a
    2b:* 3b 73 04 cmp 0x4(%ebx),%esi
    Reviewed-by: WANG Cong
    Signed-off-by: Andrew Morton
    Signed-off-by: Sam Ravnborg

    Arjan van de Ven
     

31 May, 2008

1 commit


29 Jan, 2008

1 commit


17 Jul, 2007

1 commit

  • 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
    Cc: Andi Kleen
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Randy Dunlap