gdb: Use unwinder name in frame_info::to_string
authorLancelot SIX <lsix@lancelotsix.com>
Sun, 1 Aug 2021 15:47:29 +0000 (15:47 +0000)
committerLancelot SIX <lsix@lancelotsix.com>
Wed, 4 Aug 2021 23:12:06 +0000 (23:12 +0000)
commit8085fa01a57e356aa1b91d30f89f6146ee1928c1
tree2333fe98508839422280098d4bf784f6cb079546
parent06b80590fbe63875e8e7a6c97622675b8ac099bc
gdb: Use unwinder name in frame_info::to_string

While working on a stack unwinding issue using 'set debug frame on', I
noticed the frame_info::to_string method could be slightly improved.

Unwinders have been given a name in
a154d838a70e96d888620c072e2d6ea8bdf044ca.  Before this patch, frame_info
debug output prints the host address of the used unwinder, which is not
easy to interpret.  This patch proposes to use the unwinder name
instead since we now have it.

Before the patch:

    {level=1,type=NORMAL_FRAME,unwind=0x2ac1763ec0,pc=0x3ff7fc3460,id={stack=0x3ff7ea79b0,code=0x0000003ff7fc33ac,!special},func=0x3ff7fc33ac}

With the patch:

    {level=1,type=NORMAL_FRAME,unwinder="riscv prologue",pc=0x3ff7fc3460,id={stack=0x3ff7ea79b0,code=0x0000003ff7fc33ac,!special},func=0x3ff7fc33ac}

Tested on riscv64-linux-gnu.
gdb/frame.c