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

Pierre A. Humblet Pierre.Humblet@ieee.org
Fri Dec 5 02:35:00 GMT 2003

At 03:54 PM 12/4/2003 -0500, 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.

FWIW, on WinME I get the pop up to the effect that there was a fault in
gdb doesn't kick in. 

When I ^C during makes, I can crash make more or less reliably and have 
gdb attach to it from error_start. 
A typical traceback is copied below. I poked around but found nothing obvious.
Usually the system is screwed up when I try to quit gdb and the adventure
with a reboot & scandisk.


(gdb) #0  0xbff66879 in KERNEL32!CallNamedPipeW ()
#1  0xbff6a3e1 in KERNEL32!Heap32First ()
#2  0xbff6c8c9 in ReadProcessMemory ()
#3  0xbff6c923 in ReadProcessMemory ()
#4  0x610ab22a in pthread::cancelable_wait(void*, unsigned long, bool)
xdc, timeout=4294967295, do_cancel=1) at
#5  0x610b97c8 in wait4 (intpid=-1, status=0x85ed1c, options=0, r=0x0) at
#6  0x610b9359 in wait (status=0x85ed1c) at
#7  0x6109313e in _sigfe () at
#8  0x004028d4 in _size_of_stack_reserve__ ()
#9  0x6102a24e in call_signal_handler_now () at
#10 0x610b9675 in wait4 (intpid=-1, status=0x85ee0c, options=0, r=0x0) at
#11 0x610b9359 in wait (status=0x85ee0c) at
#12 0x6109313e in _sigfe () at
#13 0x0040d9d6 in _size_of_stack_reserve__ ()
#14 0x00419e15 in _size_of_stack_reserve__ ()
(More stack frames follow...)

More information about the Cygwin-developers mailing list