From: "M.M. Kettenis" <m.m.kettenis@alumnus.utwente.nl>
To: Nick Roberts <nickrob@snap.net.nz>,
Mark Kettenis <kettenis@gnu.org>,
gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Fix broken interp.exp testcase
Date: Mon, 07 Feb 2005 20:20:00 -0000 [thread overview]
Message-ID: <7319845280102291@weblx058.utsp.utwente.nl> (raw)
In-Reply-To: <16902.64532.677951.838183@farnswood.snap.net.nz>
Nick Roberts <nickrob@snap.net.nz> wrote:
>
> > The new testcase is failing for me:
> >
> > Running ../../../src/gdb/testsuite/gdb.base/interp.exp ...
> > PASS: gdb.base/interp.exp: interpreter-exec mi "-var-update *"
> > FAIL: gdb.base/interp.exp: interpreter-exec console "show version"
> >
> > I committed the attached patch to fix it.
>
> Well it was passing for me, as it does with your patch. I must have something
> wrong with my setup.
Well, the behaviour of expect can be really odd, especially when doing
regexp matches. Nothing to really worry about; just keep it in mind.
> Running the whole testsuite, I get:
>
> === gdb Summary ===
>
> # of expected passes 10077
> # of unexpected failures 361
> # of unexpected successes 1
> # of expected failures 46
> # of known failures 60
> # of unsupported tests 11
> /home/nick/src/gdb/testsuite/../../gdb/gdb version 6.3.50.20050203-cvs -nx
>
>
> which seems an unacceptable number of fails and makes running the testsuite
> rather pointless. Have you any ideas of what I might be doing wrong?
What system is this? It seems unusually high if you're running gdb on
an up-to-date i386 GNU/Linux system, but on other systems (including
older i386 GNU/Linux) the number of failures can be fairly high because
of:
* Bugs in gdb.
* Bugs in the operating system kernel & (thread) libraries.
* Bugs in the compiler you're using.
Mark
next prev parent reply other threads:[~2005-02-07 14:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200502070239.j172dpjJ009250@copland.sibelius.xs4all.nl>
2005-02-07 17:09 ` Nick Roberts
2005-02-07 20:20 ` M.M. Kettenis [this message]
2005-02-07 14:40 Mark Kettenis
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=7319845280102291@weblx058.utsp.utwente.nl \
--to=m.m.kettenis@alumnus.utwente.nl \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@gnu.org \
--cc=nickrob@snap.net.nz \
/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