• Sasha Levin's avatar
    decode_stacktrace: make stack dump output useful again · dbd1abb2
    Sasha Levin authored
    Right now when people try to report issues in the kernel they send stack
    dumps to eachother, which looks something like this:
    
      [    6.906437]  [<ffffffff811f0e90>] ? backtrace_test_irq_callback+0x20/0x20
      [    6.907121]  [<ffffffff84388ce8>] dump_stack+0x52/0x7f
      [    6.907640]  [<ffffffff811f0ec8>] backtrace_regression_test+0x38/0x110
      [    6.908281]  [<ffffffff813596a0>] ? proc_create_data+0xa0/0xd0
      [    6.908870]  [<ffffffff870a8040>] ? proc_modules_init+0x22/0x22
      [    6.909480]  [<ffffffff810020c2>] do_one_initcall+0xc2/0x1e0
      [...]
    
    However, most of the text you get is pure garbage.
    
    The only useful thing above is the function name.  Due to the amount of
    different kernel code versions and various configurations being used,
    the kernel address and the offset into the function are not really
    helpful in determining where the problem actually occured.
    
    Too often the result of someone looking at a stack dump is asking the
    person who sent it f...
    dbd1abb2
decode_stacktrace.sh 3.01 KB