Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [patch] gdb.c++/pr-1023.exp: new test script
Date: Mon, 03 Feb 2003 18:36:00 -0000	[thread overview]
Message-ID: <20030203183645.GB27429@nevyn.them.org> (raw)
In-Reply-To: <200302031805.h13I5qA28182@duracef.shout.net>

On Mon, Feb 03, 2003 at 12:05:52PM -0600, Michael Elizabeth Chastain wrote:
> This is a new C++ test script.  It demonstrates the bug in PR gdb/1023.
> This bug is still present in gdb HEAD%20030201, so the test script
> has a KFAIL arm in it.
> 
> Testing: native i686-pc-linux-gnu, gcc v2 and v3, dwarf-2 and stabs+.
> All results are either PASS or KFAIL.  As the PR says, it KFAIL's with
> gcc 2.95.3 dwarf-2.
> 
> I will wait 24 hours and then commit this.
> 
> This is a simple test script, so it will be a good candidate for the
> new gdb_test_multiple syntax.  *After* committing this nice working
> version, I will be open to gdb_test_multiple experiments.

Sounds good.  By the way:

> setup_kfail "gdb/1023"
> 
> send_gdb "break myClass::performBlocking\n"
> gdb_expect {
>     -re "Breakpoint $decimal at $hex: file .*$srcfile, line 12.*$gdb_prompt $" {
> 	pass "break myClass::performBlocking"
>     }
>     -re "the class myClass does not have any method named performBlocking.*$gdb_prompt $" {
> 	# fails with gcc 2.95.3 -gstabs+, native i686-pc-linux-gnu
> 	# -- chastain 2003-02-03
> 	kfail "gdb/1023" "break myClass::performBlocking"
>     }

You should be using either setup_kfail or an explicit kfail, but not
both.  I think you meant the latter in this case.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-02-03 18:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-03 18:05 Michael Elizabeth Chastain
2003-02-03 18:36 ` Daniel Jacobowitz [this message]
2003-02-03 18:57 Michael Elizabeth Chastain
2003-02-05  6:44 Michael Elizabeth Chastain
2003-02-05  7:24 ` Jim Blandy

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=20030203183645.GB27429@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.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