Re: GCC snapshots and mmap problem [Re: GDB hangs on Win2K]

[Mumit Khan <khan at NanoTech dot Wisc dot EDU>]

Chris Faylor <cgf@cygnus.com> writes:
> 
> I don't understand.  If gcc is hung waiting for a resource lock, that
> will be made very clear by attaching gdb to the hung process.
> 
> I don't see why we have to go the the pain of attempting a rebuild of
> cygwin as a debugging technique.
> 

I have tried the usual methods to debug the problem, but without success 
so far. Also, it looks like it's not hung, just taking 100% of CPU, and 
I've let it run for hours. I can attach, but that's about all I seem to 
be able to do:

$ ./cc1.exe -Wall -Wno-long-long -O2 -g -pedantic fold-const-tmp.i
[ ... let it run until it gets into seemingly hangs, while using up
  100% of CPU ... ]

$ gdb -nw cc1.exe 284
Attaching to program `/cygmounts/e/gcc-2.96-cvs/BUILD/gcc/cc1.exe',process 284
77f60000:C:/WINNT/System32/ntdll.dll
61000000:c:/Cygwin/bin/cygwin1.dll
77dc0000:C:/WINNT/system32/ADVAPI32.DLL
77f00000:C:/WINNT/system32/KERNEL32.dll
77e70000:C:/WINNT/system32/USER32.dll
77ed0000:C:/WINNT/system32/GDI32.dll
77e10000:C:/WINNT/system32/RPCRT4.dll
5f810000:C:/WINNT/System32/rpcltc1.dll
[Switching to thread 284.0x12d]
0x77f76149 in ?? ()
(gdb) thread 3
[Switching to thread 3 (thread 289.0x127)]
#0  0x77f76149 in ?? ()
(gdb) where
#0  0x77f76149 in ?? ()
#1  0x77f04f2c in ?? ()
(gdb) thread
[Current thread is 3 (thread 289.0x127)]
(gdb) thread 1
[Switching to thread 1 (thread 289.0x123)]
#0  0x61023023 in _size_of_stack_reserve__ ()
(gdb) where
#0  0x61023023 in _size_of_stack_reserve__ ()
Cannot access memory at address 0x2000000

I'm going to try this out with a debuggable DLL and see if I can get
anywhere. Using Cygwin 1.1.0 gdb or your current dev one produces the
same problem.

Regards,
Mumit


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com