From: Nick Roberts <nickrob@snap.net.nz>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb@sourceware.org
Subject: Re: [ANNOUNCEMENT] GDB 6.8 release process created!
Date: Sat, 01 Mar 2008 22:21:00 -0000 [thread overview]
Message-ID: <18377.54973.885633.998260@kahikatea.snap.net.nz> (raw)
In-Reply-To: <ud4qekc8t.fsf@gnu.org>
> It builds okay, and yields the results below for "make check":
>
> === gdb Summary ===
>
> # of expected passes 11833
> # of unexpected failures 73
> # of unexpected successes 2
> # of expected failures 43
> # of known failures 39
> # of untested testcases 10
> # of unsupported tests 49
>
> If someone wants to know details about some specific test cases, I
> have the data available, just holler.
That seems like a lot of failures. Are any of these the ones Vladimir
pointed out?:
FAIL: gdb.base/annota1.exp: continue to printf
FAIL: gdb.base/annota1.exp: send SIGUSR1
FAIL: gdb.base/annota1.exp: signal sent
FAIL: gdb.cp/annota2.exp: continue to exit
FAIL: gdb.cp/annota2.exp: watch triggered on a.x
He says:
> JFYI -- I'm not sure we should bother about annotations.
If that's to wind me up - that's fine, I probably can't expect any more,
but I hope it's not GDB policy.
In this particular case, it's not a problem because Emacs doesn't use
frames-invalid annotations - but it does use others.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2008-03-01 22:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-29 18:55 Joel Brobecker
2008-02-29 22:25 ` Thiago Jung Bauermann
2008-03-01 0:20 ` Joel Brobecker
2008-03-01 1:16 ` Daniel Jacobowitz
2008-03-03 17:30 ` Thiago Jung Bauermann
2008-03-01 9:47 ` Eli Zaretskii
2008-03-01 22:21 ` Nick Roberts [this message]
2008-03-02 3:59 ` Daniel Jacobowitz
2008-03-02 4:24 ` Eli Zaretskii
2008-03-02 4:22 ` Eli Zaretskii
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=18377.54973.885633.998260@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=eliz@gnu.org \
--cc=gdb@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