[f]statvfs (was Re: bug in statfs)

Brian Ford ford@vss.fsi.com
Thu Dec 4 21:17:00 GMT 2003

On Thu, 4 Dec 2003, Christopher Faylor wrote:

> On Thu, Dec 04, 2003 at 12:52:31PM -0600, Brian Ford wrote:
> >PS. I'm still seeing random silent "deaths" with the current cvs
> >cygwin1.dll.  Long configure scripts randomly stop in the middle.
> >Re-running them, they might complete, or they might stop in a different
> >spot.  Even configuring/compiling Cygwin again is then a hit and miss
> >proposition.  Does anyone else see this or have an idea how to debug it?
> set CYGWIN=error_start=x:\path\gdb
> I doubt that they are just silent exits.
ford@fordpc ~/downloads/ddd-3.3.8
$ ./configure
checking build system type... i686-pc-cygwin
checking host system type... i686-pc-cygwin
checking target system type... i686-pc-cygwin
checking for product name... DDD 3.3.8 "Cinnamon"
checking for expiration date... no
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets ${MAKE}... yes
checking whether make sets ${MAKE}... (cached) yes
checking for style of include used by make... GNU
checking for gcc... gcc
checking for C compiler default output... a.exe
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... .exe
checking for suffix of object files...
ford@fordpc ~/downloads/ddd-3.3.8
$ echo $CYGWIN
tty ntsec error_start=G:\cygwin\bin\gdb.exe

Did I miss something, or what next?

Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax:   314-551-8444

More information about the Cygwin-developers mailing list