Re: [Bashdb-devel] bashdb 3.1-0.08 test failures under cygwin

[Eric B. <eb...@by...>]

According to Rocky Bernstein on 4/24/2007 2:08 AM:
> I've just compiled bash 3.2.15 on GNU/Linux (with gcc version 4.1.0 and=
=20
> -O2 optimization). I was able to run the regression tests without any
> errors both on bashdb 3.1-0.08 and current CVS sources.
>=20
> On cygwin where I noticed a failure, I was using the installed bash fro=
m
> the Interent. Furthermore  bashdb wasn't using readarray the C-compiled=

> extension.

Have you had any success getting cygwin bash to use loadable modules, suc=
h
as readarray?

>=20
> Given this, right now the evidence suggests that the problem mentioned
> in this thread is in the bash 3.2.15 binary on cygwin.

Indeed it was.  There are latent bugs in the bash source code, where
various builtins leak output to the wrong file if stdio is not line
buffered; but cygwin bash had a local patch that did just that in order t=
o
fix another bug where builtins incorrectly used text mode instead of
binary mode to talk over pipes.  I've uploaded a new version of bash for
cygwin that has the problem with builtins fixed, and verified that the
bashdb testsuite passes again.

--=20
Don't work too hard, make some time for fun as well!

Eric Blake             eb...@by...