From: Tom Tromey <tromey@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH 1/2] Test case for entry values.
Date: Tue, 20 Aug 2013 17:39:00 -0000 [thread overview]
Message-ID: <87wqnggt2i.fsf@fleche.redhat.com> (raw)
In-Reply-To: <1376379586-24150-2-git-send-email-yao@codesourcery.com> (Yao Qi's message of "Tue, 13 Aug 2013 15:39:45 +0800")
>>>>> "Yao" == Yao Qi <yao@codesourcery.com> writes:
Yao> This is a test case for "entry-values" in an arch-independent way. The
Yao> first part of entry-values.exp is to calculate the length of functions
Yao> and the offset of instruction call in function bar. Then, this test
Yao> uses Dwarf Assembler to emit some DIEs for "entry-values".
Thanks Yao. This is cool.
Yao> +# Start GDB and load object file, compute the function length and
Yao> +# the offset of branch instruction in function. They are needed
Yao> +# in the Dwarf Assembler below.
Nice technique! I'll have to use that.
Yao> +# Calculate the offset of the last instruction from the beginning.
Yao> +set test "disassemble foo"
Yao> +gdb_test_multiple $test $test {
Yao> + -re ".*$hex <\\+($decimal)>:\[^\r\n\]+\r\nEnd of assembler dump\.\r\n$gdb_prompt $" {
Yao> + set foo_length $expect_out(1,string)
Yao> + pass $test
Yao> + }
Yao> + -re ".*$gdb_prompt $" {
Yao> + fail $test
Yao> + }
Yao> +}
If this test fails then later on foo_length won't be set.
This will yield a Tcl error in the test suite.
It's probably better to just bail out here.
I think this applies elsewhere too.
Yao> + cu {addr_size 4} {
Will it still work on x86-64?
Tom
next prev parent reply other threads:[~2013-08-20 17:39 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 7:41 [PATCH 0/2] Test case on " Yao Qi
2013-08-13 7:41 ` [RFC 2/2] Test entry values in trace frame Yao Qi
2013-08-20 17:48 ` Tom Tromey
2013-08-21 6:06 ` Yao Qi
2013-08-21 14:35 ` [PATCH] PR gdb/15871: Unavailable entry value is not shown correctly Pedro Alves
2013-08-21 14:47 ` Mark Kettenis
2013-08-21 15:32 ` Pedro Alves
2013-08-21 15:43 ` Mark Kettenis
2013-08-22 1:25 ` Yao Qi
2013-08-22 10:04 ` [COMMIT] " Pedro Alves
2013-08-23 1:08 ` Yao Qi
2013-08-23 16:50 ` Pedro Alves
2013-08-23 0:32 ` [RFC 2/2] Test entry values in trace frame Yao Qi
2013-08-23 17:04 ` Pedro Alves
2013-08-23 19:16 ` Tom Tromey
2013-08-24 1:56 ` Yao Qi
2013-08-13 7:41 ` [PATCH 1/2] Test case for entry values Yao Qi
2013-08-20 17:39 ` Tom Tromey [this message]
2013-08-21 5:55 ` Yao Qi
2013-08-21 15:02 ` Tom Tromey
2013-08-22 0:12 ` Yao Qi
2013-08-22 14:05 ` Tom Tromey
2013-08-23 0:27 ` Yao Qi
2013-08-23 19:23 ` Tom Tromey
2013-08-24 1:56 ` Yao Qi
2013-08-30 14:52 ` Vidya Praveen
2013-08-30 15:29 ` Vidya Praveen
2013-08-31 0:22 ` Yao Qi
2013-09-10 15:30 ` Vidya Praveen
2013-09-10 23:44 ` Yao Qi
2013-09-11 13:27 ` Vidya Praveen
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=87wqnggt2i.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=yao@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