This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: 1.7.5-1: execv fails in .exe compiled
The problem appears to be cygwin 1.7-specific. (*)
I get a stackdump as follows. I find that I get a stackdump under a
cygwin shell (DOS terminal) but not under mintty so I'm not 100% sure
the stackdump is for the correct error.
Exception: STATUS_ACCESS_VIOLATION at eip=611131D8
eax=0022B9E4 ebx=7FF70008 ecx=00000063 edx=0022B9E4 esi=00000001 edi=00000005
ebp=0022B998 esp=0022B950
program=C:\usr\local\companytools\gcc34\x86\cc386.exe, pid 1312,
thread main
cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023
Stack trace:
Frame Function Args
0022B998 611131D8 (0022D000, 7FF70008, 10029448, 00000005)
0022B9F8 610C953E (00008000, 10029448, 00000005, 00000001)
1002944D 6103413C (68000000, 46611C2F, 68DF0DF0, 00100280)
End of stack trace
I was able to get a further stack trace from gdb from that. Again, it
would only happen on a cygwin shell and not mintty so I'm not sure I
copied the correct error:
(gdb) backtrace
#0 0x7c90120f in ?? ()
#1 0x7c951e68 in ?? ()
#2 0x00000005 in ?? ()
#3 0x00000004 in ?? ()
#4 0x00000001 in ?? ()
#5 0x006dffd0 in ?? ()
#6 0x00000246 in ?? ()
#7 0xffffffff in ?? ()
#8 0x7c90e920 in ?? ()
#9 0x7c951e88 in ?? ()
#10 0x00000000 in ?? ()
Stephen
(*) I know that doesn't mean that it's 1.7's fault. Perhaps the
problem was pre-existing and was only revealed in 1.7. But it works in
1.3 and 1.5 on WinXP and fails in 1.7 in WinXP-32, Vista-32, Win7-67.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple