Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Elizabeth Chastain <mec@shout.net>
To: carlton@math.stanford.edu, gdb-patches@sources.redhat.com
Subject: Re: [patch] kfail gdb.c++/annota2.exp annotate-quit
Date: Thu, 19 Dec 2002 07:42:00 -0000	[thread overview]
Message-ID: <200212190547.gBJ5lnN24237@duracef.shout.net> (raw)

My testbed gives me 34 KFAIL's on 34 configurations, just fine.
This is native i686-pc-linux-gnu, gcc v2 and v3, dwarf-2 and stabs+.

I use stock FSF dejagnu 1.4.3.  I also built dejagnu from the
sourcware cvs "dejagnu" module and did a test run with that.
That works fine too.

I have appended a gdb.sum file for anyone who is curious.
The KFAIL line looks like this:

  KFAIL: gdb.c++/annota2.exp: annotate-quit (PRMS: c++/544)

We can't do anything about the "PRMS:" part, that comes from dejagnu.

I have an objection to the name "c++/544".  It is way too easy for
this name to get quoted out of context (the context being that it is
a gdb bug in the gdb database).  I think this will cause confusion.
I would like to see "gdb/544" here.

Sure, right *now* while we are discussing the issue, everyone knows
that "c++/544" means a gdb bug in the gdb PR database.  Wait six weeks
and then quote some people a gdb.sum report that says "c++/482" in it
and see if anyone jumps to the incorrect conclusion that c++/482 means
a bug in the C++ compiler.

Michael C

===

Test Run By mec on Thu Dec 19 00:20:19 2002
Native configuration is i686-pc-linux-gnu

		=== gdb tests ===

Schedule of variations:
    unix/gdb:debug_flags=-gdwarf-2

Running target unix/gdb:debug_flags=-gdwarf-2
Running /berman/fsf/_today_/source/gdb/HEAD/src/gdb/testsuite/gdb.c++/annota2.exp ...
PASS: gdb.c++/annota2.exp: breakpoint main
PASS: gdb.c++/annota2.exp: annotation set at level 2
PASS: gdb.c++/annota2.exp: run until main breakpoint
PASS: gdb.c++/annota2.exp: print class
PASS: gdb.c++/annota2.exp: continue until exit
PASS: gdb.c++/annota2.exp: delete bps
PASS: gdb.c++/annota2.exp: breakpoint at main
PASS: gdb.c++/annota2.exp: run until main breakpoint
PASS: gdb.c++/annota2.exp: set watch on a.x
FAIL: gdb.c++/annota2.exp: watch triggered on a.x
KFAIL: gdb.c++/annota2.exp: annotate-quit (PRMS: c++/544)

		=== gdb Summary ===

# of expected passes		9
# of unexpected failures	1
# of known failures		1
/berman/fsf/_today_/berman/native/install/gdb/HEAD/bin/gdb version  2002-12-12-cvs -nx


             reply	other threads:[~2002-12-19  5:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-19  7:42 Michael Elizabeth Chastain [this message]
2002-12-19 11:01 ` David Carlton
2002-12-19 13:48 ` Daniel Jacobowitz
2002-12-20  9:12   ` Andrew Cagney
2002-12-20 10:09     ` Daniel Jacobowitz
2002-12-20 10:50       ` David Carlton
  -- strict thread matches above, loose matches on Subject: below --
2002-12-18 20:57 David Carlton

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=200212190547.gBJ5lnN24237@duracef.shout.net \
    --to=mec@shout.net \
    --cc=carlton@math.stanford.edu \
    --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