[Cygwin64] make segfault

[Peter Rosin]

Hi!

Sure looks familiar, but it's make this time...

$ uname -a
CYGWIN_NT-6.1 PEDA-PC 1.7.18(0.263/5/3) 2013-03-13 11:11 x86_64 Cygwin

Cheers,
Peter



Reading symbols from /usr/bin/make.exe...(no debugging symbols found)...done.
Attaching to program `/usr/bin/make.exe', process 45412
[New Thread 45412.0x5360]
[New Thread 45412.0x41b0]
[New Thread 45412.0xa8f4]
[New Thread 45412.0x2fe0]
[New Thread 45412.0x48e8]
(gdb) t a a bt

Thread 5 (Thread 45412.0x48e8):
#0 0x0000000076eb0531 in ntdll!DbgBreakPoint ()
from /cygdrive/c/Windows/SYSTEM32/ntdll.dll
#1 0x0000000076f57ef8 in ntdll!DbgUiRemoteBreakin ()
from /cygdrive/c/Windows/SYSTEM32/ntdll.dll
#2 0x0000000000000000 in ?? ()

Thread 4 (Thread 45412.0x2fe0):
#0 0x0000000076eb135a in ntdll!ZwWaitForSingleObject ()
from /cygdrive/c/Windows/SYSTEM32/ntdll.dll
#1 0x000007fefd4b10dc in WaitForSingleObjectEx ()
from /cygdrive/c/Windows/system32/KERNELBASE.dll
#2 0x0000000000000000 in ?? ()

Thread 3 (Thread 45412.0xa8f4):
#0 0x0000000076eb135a in ntdll!ZwWaitForSingleObject ()
from /cygdrive/c/Windows/SYSTEM32/ntdll.dll
#1 0x000007fefd4b10dc in WaitForSingleObjectEx ()
from /cygdrive/c/Windows/system32/KERNELBASE.dll
#2 0x0000000000000000 in ?? ()

Thread 2 (Thread 45412.0x41b0):
#0 0x0000000076eb137a in ntdll!ZwReadFile ()
---Type <return> to continue, or q <return> to quit---
from /cygdrive/c/Windows/SYSTEM32/ntdll.dll
#1 0x000007fefd4b1a7a in ReadFile ()
from /cygdrive/c/Windows/system32/KERNELBASE.dll
#2 0x000000000022ce00 in ?? ()
#3 0x00000001802daa48 in fhandler_disk_file::isdevice ()
from /usr/bin/cygwin1.dll
#4 0x000000010040bbf0 in ?? ()
#5 0x0000000000000005 in ?? ()
#6 0x00000000005caa40 in ?? ()
#7 0x00000000005caaf0 in ?? ()
#8 0x00000000000000b0 in ?? ()
#9 0x0000000000000000 in ?? ()

Thread 1 (Thread 45412.0x5360):
#0 0x0000000076eb0940 in ntdll!RtlRestoreContext ()
from /cygdrive/c/Windows/SYSTEM32/ntdll.dll
#1 0x0000000076eb1286 in ntdll!KiUserExceptionDispatcher ()
from /cygdrive/c/Windows/SYSTEM32/ntdll.dll
#2 0x0000000000228e70 in ?? ()
#3 0x0000000000228980 in ?? ()
#4 0x0000000000000000 in ?? ()
(gdb)

[Corinna Vinschen]

Post by Peter Rosin
Hi!
Sure looks familiar, but it's make this time...
$ uname -a
CYGWIN_NT-6.1 PEDA-PC 1.7.18(0.263/5/3) 2013-03-13 11:11 x86_64 Cygwin
Cheers,
Peter
Reading symbols from /usr/bin/make.exe...(no debugging symbols found)...done.
Attaching to program `/usr/bin/make.exe', process 45412
[New Thread 45412.0x5360]
[New Thread 45412.0x41b0]
[New Thread 45412.0xa8f4]
[New Thread 45412.0x2fe0]
[New Thread 45412.0x48e8]
(gdb) t a a bt

Such a GDB backtrace is really not useful without additional
information, unless it shows a clear path to the error. It's not
even visibale which thread died. A stackdump file would probably
give more useful information than a GDB backtrace.

Btw, I uploaded new version of make and the cygwin package today.
Please switch to them.


Corinna