From: Tom Tromey <tromey@redhat.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: DW_OP_call_frame_cfa, again
Date: Wed, 02 Sep 2009 16:48:00 -0000 [thread overview]
Message-ID: <m3pra9nvib.fsf@fleche.redhat.com> (raw)
In-Reply-To: <200909021559.24406.pedro@codesourcery.com> (Pedro Alves's message of "Wed, 2 Sep 2009 15:59:24 +0100")
>>>>> "Pedro" == Pedro Alves <pedro@codesourcery.com> writes:
Pedro> Please don't hardcode "run". It won't work with remote targets
Pedro> (e.g., gdbserver).
Sorry about that.
This uses runto_main and gdb_continue_to_breakpoint, which should work
everywhere, at least if other tests are any indication.
Tom
2009-09-02 Tom Tromey <tromey@redhat.com>
* gdb.dwarf2/callframecfa.exp: Use gdb_continue_to_breakpoint.
Index: gdb.dwarf2/callframecfa.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.dwarf2/callframecfa.exp,v
retrieving revision 1.1
diff -u -r1.1 callframecfa.exp
--- gdb.dwarf2/callframecfa.exp 2 Sep 2009 14:53:57 -0000 1.1
+++ gdb.dwarf2/callframecfa.exp 2 Sep 2009 16:32:22 -0000
@@ -44,8 +44,12 @@
gdb_reinitialize_dir $srcdir/$subdir
gdb_load ${binfile}
-gdb_test "break *func" "Breakpoint 1.*" "set breakpoint for call-frame-cfa"
-gdb_test "run" "" "run for call-frame-cfa"
+if ![runto_main] {
+ return -1
+}
+
+gdb_test "break *func" "Breakpoint 2.*" "set breakpoint for call-frame-cfa"
+gdb_continue_to_breakpoint "continue to breakpoint for call-frame-cfa"
gdb_test "display arg" "arg = 77" "set display for call-frame-cfa"
# We know how many instructions are in the function. Note that we
next prev parent reply other threads:[~2009-09-02 16:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-12 0:52 Tom Tromey
2009-09-01 18:08 ` Tom Tromey
2009-09-01 23:07 ` Doug Evans
2009-09-01 23:41 ` Tom Tromey
2009-09-01 23:24 ` Pedro Alves
2009-09-01 23:47 ` Tom Tromey
2009-09-02 14:53 ` Tom Tromey
2009-09-02 14:59 ` Pedro Alves
2009-09-02 16:48 ` Tom Tromey [this message]
2009-09-02 17:01 ` Pedro Alves
2009-09-01 22:50 ` Daniel Jacobowitz
2009-09-01 23:51 ` Tom Tromey
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=m3pra9nvib.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
/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