From: Peng Yu <pengyu.ut@gmail.com>
To: libc-help <libc-help@sourceware.org>
Subject: Does glibc has complete test coverage?
Date: Tue, 23 Mar 2021 11:39:14 -0500 [thread overview]
Message-ID: <CABrM6wmfgYF_s2zOwpiGJKyRAT5+69ZOR8bSSPasXf+N0zPMUg@mail.gmail.com> (raw)
Hi,
https://www.kernel.org/doc/man-pages/missing_pages.html
"... quite a few kernel and glibc bugs have been uncovered while
writing test programs during the preparation of man pages. "
I see the above text. It doesn't make too much sense, as it indicates
that glibc does not have complete test coverage.
Why not taking an approach of always accompanying each line of source
code with appopriate test cases? If this approach is taken, then most
bugs should have been eliminated beforehand?
--
Regards,
Peng
next reply other threads:[~2021-03-23 16:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 16:39 Peng Yu [this message]
2021-03-23 20:41 ` Mike Frysinger
2021-03-23 21:02 ` Jeffrey Walton
2021-03-23 23:09 ` Peng Yu
2021-03-24 1:17 ` Mike Frysinger
2021-03-24 1:13 ` Mike Frysinger
2021-03-24 3:13 ` Peng Yu
2021-03-24 12:31 ` Adhemerval Zanella
2021-03-24 8:32 ` tomas
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=CABrM6wmfgYF_s2zOwpiGJKyRAT5+69ZOR8bSSPasXf+N0zPMUg@mail.gmail.com \
--to=pengyu.ut@gmail.com \
--cc=libc-help@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).