From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: gdb-patches@sourceware.org
Subject: [patch] Fix disassemble without parameters in tailcall frame
Date: Wed, 12 Sep 2012 15:38:00 -0000 [thread overview]
Message-ID: <20120912153830.GA7317@host2.jankratochvil.net> (raw)
Hi,
when the current frame is in tailcall function:
disassemble
No function contains program counter for selected frame.
(gdb) FAIL: gdb.arch/amd64-entry-value.exp: disassemble
->
disassemble
Dump of assembler code for function b(int, double):
0x0000000000400790 <+0>: addsd 0x298(%rip),%xmm0 # 0x400a30
0x0000000000400798 <+8>: add $0x2,%edi
0x000000000040079b <+11>: jmp 0x400770 <c(int, double)>
End of assembler dump.
Such a simple but annoying to me issue when tailcall frames are common in
practice now.
The "=> " PC pointer is now not displayed anywhere which seems correct to me.
No regressions on {x86_64,x86_64-m32,i686}-fedora18-linux-gnu.
Thanks,
Jan
gdb/
2012-09-12 Jan Kratochvil <jan.kratochvil@redhat.com>
Fix disassemble without parameters in tailcall frame.
* cli/cli-cmds.c (disassemble_current_function): Use
get_frame_address_in_block.
gdb/testsuite/
2012-09-12 Jan Kratochvil <jan.kratochvil@redhat.com>
Fix disassemble without parameters in tailcall frame.
* gdb.arch/amd64-entry-value.exp (down, disassemble): New tests.
diff --git a/gdb/cli/cli-cmds.c b/gdb/cli/cli-cmds.c
index d3473d5..0bdd373 100644
--- a/gdb/cli/cli-cmds.c
+++ b/gdb/cli/cli-cmds.c
@@ -1091,7 +1091,7 @@ disassemble_current_function (int flags)
frame = get_selected_frame (_("No frame selected."));
gdbarch = get_frame_arch (frame);
- pc = get_frame_pc (frame);
+ pc = get_frame_address_in_block (frame);
if (find_pc_partial_function (pc, &name, &low, &high) == 0)
error (_("No function contains program counter for selected frame."));
#if defined(TUI)
diff --git a/gdb/testsuite/gdb.arch/amd64-entry-value.exp b/gdb/testsuite/gdb.arch/amd64-entry-value.exp
index dd22d42..5ff18bf 100644
--- a/gdb/testsuite/gdb.arch/amd64-entry-value.exp
+++ b/gdb/testsuite/gdb.arch/amd64-entry-value.exp
@@ -213,6 +213,10 @@ gdb_test {p $sp0 == $sp} " = true"
gdb_test "frame 3" "\r\n#3 .*"
gdb_test {p $sp0 + sizeof (void *) == $sp} " = true"
+# Test $pc adjustment which is now right after the function end.
+gdb_test "down" "\r\n#2 .*"
+gdb_test "disassemble" {Dump of assembler code for function b\(int, double\):.*}
+
# Test partial-ambiguous virtual tail call frames chain.
next reply other threads:[~2012-09-12 15:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-12 15:38 Jan Kratochvil [this message]
2012-09-13 3:56 ` Yao Qi
2012-09-13 4:17 ` Jan Kratochvil
2012-09-21 19:35 ` [commit] " Jan Kratochvil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120912153830.GA7317@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox