• Davi Arnaut's avatar
    Bug#41612: resolve_stack_dump does not decode 5.1 stack trace · d6e7b04a
    Davi Arnaut authored
    resolve_stack_dump is not able to decode a stack trace produced
    by glibc's backtrace() functions. The problem is that the stack
    trace addresses are printed between brackets and the utility is
    not able to ignore the brackets.
    
    The solution is to modify resolve_stack_dump so it can recognize
    stack trace addresses surrounded by brackets. e.g. [0xdeadbeef].
    d6e7b04a
resolve_stack_dump.c 7.48 KB