Make "set disassemble-next-line on" can work with DUMMY_FRAME, SIGTRAMP_FRAME and...
authorHui Zhu <teawater@gmail.com>
Sun, 27 Apr 2014 14:23:43 +0000 (22:23 +0800)
committerHui Zhu <teawater@gmail.com>
Sun, 27 Apr 2014 14:23:43 +0000 (22:23 +0800)
commit433e77fad1fda55408db072de18dcd4f9116289e
tree9f5e294f637d19220767412a3e87ce0bc74fb683
parent7b667436a52c584267cc78d1fbc05c84856192ee
Make "set disassemble-next-line on" can work with DUMMY_FRAME, SIGTRAMP_FRAME and ARCH_FRAME

When GDB debug DUMMY_FRAME, SIGTRAMP_FRAME and ARCH_FRAME, even if
"set disassemble-next-line on", it will not output the asm code:
(gdb) set disassemble-next-line on
(gdb) si
<signal handler called>
(gdb)
<signal handler called>
(gdb)
<signal handler called>

So make this patch make they can work together, it will become:
(gdb) si
<signal handler called>
=> 0xffffffff816bfb09 <int_with_check+0>: 65 48 8b 0c 25 c8 c7 00 00 mov    %gs:0xc7c8,%rcx
(gdb)
<signal handler called>
=> 0xffffffff816bfb12 <int_with_check+9>: 48 81 e9 d8 1f 00 00 sub    $0x1fd8,%rcx
(gdb)
<signal handler called>
=> 0xffffffff816bfb19 <int_with_check+16>: 8b 51 10 mov    0x10(%rcx),%edx

2014-04-27  Hui Zhu  <hui@codesourcery.com>

* stack.c (print_frame_info): Call do_gdb_disassembly with
DUMMY_FRAME, SIGTRAMP_FRAME and ARCH_FRAME.
gdb/ChangeLog
gdb/stack.c