From: Benjamin Kosnik <bkoz@redhat.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: gdb-patches@sources.redhat.com
Subject: Re: gdb.c++ testsuite 2.1: try_catch.exp
Date: Tue, 28 May 2002 08:59:00 -0000 [thread overview]
Message-ID: <20020528085804.256cadb0.bkoz@redhat.com> (raw)
In-Reply-To: <200205271924.g4RJOJw27502@duracef.shout.net>
> There was a cut-and-paste error here (line 122 versus line 118):
>
> send_gdb "break 122\n"
> gdb_expect {
> -re "Breakpoint \[0-9\]*.*line 118\\.\r\n$gdb_prompt $" {
> ...
>
> I rewrote all the send_gdb/gdb_expect pairs to gdb_test.
> This simplifies the test script a lot:
>
> gdb_test "break 61" "Breakpoint \[0-9\]*.*line 61\\."
> gdb_test "continue"
> "Continuing\\.\r\n\r\nBreakpoint.*at.*try_catch\\.cc:61\r\n.*"
> "continue to 61"
Looks good, thanks for your additions.
> The actual tests are very simple. They don't test any of the
> try/catch functionality in gdb, just the control flow of the target
> program. A simple test is better than no test; someone can add more
> tests to this later.
Right. Actually, this has not worked in the past, so I thought it'd be
best to start with the basics.
> All the tests pass in all the configurations that I tested:
Great.
next prev parent reply other threads:[~2002-05-28 15:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-27 12:34 Michael Elizabeth Chastain
2002-05-28 8:59 ` Benjamin Kosnik [this message]
2002-05-28 18:05 ` Andrew Cagney
2002-05-28 18:49 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2002-05-29 3:00 Michael Elizabeth Chastain
2002-05-27 14:41 Michael Elizabeth Chastain
2002-05-27 6:20 Benjamin Kosnik
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=20020528085804.256cadb0.bkoz@redhat.com \
--to=bkoz@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec@shout.net \
/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