Path: csiph.com!goblin3!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail
From: Peng Yu <pengyu.ut@gmail.com>
Newsgroups: gnu.bash.bug
Subject: Re: How to compile hashlib.c for testing?
Date: Sat, 29 Dec 2018 16:44:03 -0600
Lines: 14
Approved: bug-bash@gnu.org
Message-ID: <mailman.6532.1546123750.1284.bug-bash@gnu.org>
References: <CABrM6wm+x0hGuSVYeRLSE9=6vuadxP++4+gSoG+Tm7_yYN4Duw@mail.gmail.com> <31ae9367-7968-aff5-d0e8-0f9da667d584@case.edu> <CABrM6w=a7NyF8xBkooeJojkAK_b=_rz9VsnWt2MWV3HN4BA9Eg@mail.gmail.com> <2d74e9ca-ae78-4661-ec86-36645ffa8047@case.edu>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
X-Trace: usenet.stanford.edu 1546123751 7523 208.118.235.17 (29 Dec 2018 22:49:11 GMT)
X-Complaints-To: action@cs.stanford.edu
Cc: bug-bash <bug-bash@gnu.org>
To: Chester Ramey <chet.ramey@case.edu>
Envelope-to: bug-bash@gnu.org
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=G0B6wWLrP8eosJvtRrMcOeC8ppoCEY7EQdx6d0U9ELY=; b=s16c6Q6xCyatQFBBVnrTYOrAWBtxxC6om57f3A6MIWy4pMVNwo+iw8cuk8p2ZrWk80 zCXii+cFqr5CUGjGnHJZZ5stHfBdDG4JwNsCIq8T/QIWiGifdwS/XqRT2YWqOvIe4Hjm dZ+cuHjYpOOhJnnogy0BUtUqU/qLz7Vw6dzHytm0Y7zIneAPbiKrmszrEddij3LdItOU Gt2VD8nz3yYIj6zvFIea301y9OD0/gFwDbP/0wDQtl0o6tBsjwfP30xJ0BS2B556ypWE OIL7Az6U9rhkxdpPSaFTOacyTJzowWdi/GAUnZZbAPuAEUqEkJh1YatW7V3MKLFKBK9f JyuA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=G0B6wWLrP8eosJvtRrMcOeC8ppoCEY7EQdx6d0U9ELY=; b=RVWtdj9Zfgnpa3SuY+paGjN2E1SpkV33QjysInsoBiYnBS0j57ITfYWb9oXlYQAceD kqp8UFjsxgPfYp7/WQC6ZOlG2PINN73piZ6dIWmms+0EgDYpu81qoDs571CRWsz52oJh 5mZTSfrVOgdet4sLupUmbvTbXfxDi/lXLFCLTd0DatNmCorm7MrAFqWpE6KJFkbhaaAg qm1AWdd78tZzysLfmbqhFHRFz3TqCTG+/gcye+rudkPejT9Catrp1FAGUbNTQ7oNdRhp EZQ4qjvzvpBF835W4as5beVBZ58kudyAeC/Rp+xajN6xTLU2sAnm9imwrXD0M0QDvXFs 2CqA==
X-Gm-Message-State: AA+aEWaaqYkt3DOdQM5CA8+gbOxm0Qn3tAT6eSevt8RS5THDnrZfUTo6 QHSSzqEoJRoeQ/H4dq/jnZSr3KemqULh5cKIG5zz6A==
X-Google-Smtp-Source: AFSGD/Xobwy222rJ93mHv6SBhWxifHvrisS2JMXTr+RLgUzTw1csBJ6Lxz8+b+NA8CUrR1L19G9EFHxj852V3+CqguI=
X-Received: by 2002:a24:648f:: with SMTP id t137mr19466376itc.176.1546123456065; Sat, 29 Dec 2018 14:44:16 -0800 (PST)
In-Reply-To: <2d74e9ca-ae78-4661-ec86-36645ffa8047@case.edu>
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized.
X-Received-From: 2607:f8b0:4864:20::134
X-BeenThere: bug-bash@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: Bug reports for the GNU Bourne Again SHell <bug-bash.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/bug-bash/>
List-Post: <mailto:bug-bash@gnu.org>
List-Help: <mailto:bug-bash-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=subscribe>
Xref: csiph.com gnu.bash.bug:15007

> That code hasn't really changed in almost twenty years. All the testing
> was done long ago.

Do you keep all the testing code in the bash repository? Or you keep
the testing code separately from the bash source? Given the fugal
testing code that is in the bash source, it is doesn't seem that the
current testing code can cover all the branches of the source code. I
am wondering how to ensure the code contains as few bugs as possible
without full coverage testing cases? Thanks.

-- 
Regards,
Peng