From: Daniel Jacobowitz <drow@false.org>
To: Andrew STUBBS <andrew.stubbs@st.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Command trace testsuite
Date: Tue, 08 Aug 2006 17:34:00 -0000 [thread overview]
Message-ID: <20060808173357.GA24191@nevyn.them.org> (raw)
In-Reply-To: <44D772B2.5090301@st.com>
On Mon, Aug 07, 2006 at 06:04:50PM +0100, Andrew STUBBS wrote:
> Here is a set of tests for the 'set trace-commands' command that I added
> a while back.
Thanks!
> +# Source the script with verbose mode.
> +gdb_test "source -v tracecommandsscript" {source -v tracecommandsscript[\r\n]+\+echo in tracecommandsscript\\n[\r\n]+in tracecommandsscript[\r\n]+\+define func[\r\n]+\+if 1[\r\n]+\+\+if 2[\r\n]+\+\+\+if 3[\r\n]+\+\+\+\+if 4[\r\n]+\+\+\+\+\+echo deep\\n[\r\n]+deep[\r\n]+\+\+\+\+\+func 999[\r\n]+\+\+\+\+\+\+echo in func 999\\n[\r\n]+in func 999} "source -v"
For this sort of test, there's gdb_expect_list. The nice thing about
that is that it will tell you where there's a problem on errors (and
not generate thousand-character lines). Could you give that a try?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-08-08 17:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-07 17:05 Andrew STUBBS
2006-08-08 17:34 ` Daniel Jacobowitz [this message]
2006-08-10 16:16 ` Andrew STUBBS
2006-08-10 17:12 ` Daniel Jacobowitz
2006-08-10 19:13 ` Andrew STUBBS
2006-08-10 20:30 ` Eli Zaretskii
2006-08-14 7:32 ` Andrew STUBBS
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=20060808173357.GA24191@nevyn.them.org \
--to=drow@false.org \
--cc=andrew.stubbs@st.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