Davi Arnaut b4c40ac240 Bug#41612: resolve_stack_dump does not decode 5.1 stack trace ...

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].

extra/resolve_stack_dump.c:
  Skip to after a bracket if one is present in the input.

2008-12-19 08:47:28 -02:00

7.5 KiB

Raw Blame History

View Raw