[1.7.13] STATUS_ACCESS_VIOLATION when running cygwin programs in NAnt scripts

[1.7.13] STATUS_ACCESS_VIOLATION when running cygwin programs in NAnt scripts

[Andre Loker]

Hello,

On a new system with a clean 1.7.13 installation (CYGWIN_NT-6.1-WOW64 
rs200313 1.7.13(0.260/5/3) 2012-04-05 12:43 i686 Cygwin) I'm getting 
STATUS_ACCESS_VIOLATIONs whenever I try to run any cygwin program as 
part of a NAnt* build script.

E.g. if I try to execute:
c:\cygwin\bin\bash.exe --login /cygdrive/c/Backup/syncvia.sh

I get

      [exec] C:\Backup>c:\cygwin\bin\bash.exe --login 
/cygdrive/c/Backup/syncvia.sh
      [exec]       0 [main] bash 3468 exception::handle: Exception: 
STATUS_ACCESS_VIOLATION
      [exec]     774 [main] bash 3468 open_stackdumpfile: Dumping stack 
trace to bash.exe.stackdump

Here's the stackdump file:
Exception: STATUS_ACCESS_VIOLATION at eip=61029E40
eax=00000000 ebx=0028ABCC ecx=20000668 edx=61188348 esi=00000000 
edi=00010000
ebp=00000000 esp=0028AB40 program=c:\cygwin\bin\bash.exe, pid 3732, 
thread main
cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B
Stack trace:
Frame     Function  Args
End of stack trace

I have tried to execute other cygwin programs with similar results.

However, if I run the cygwin programs from a cmd prompt or in a shell 
everything works fine.
Also, on another machine that uses the same script but runs
CYGWIN_NT-6.1-WOW64 CT50796 1.7.11(0.260/5/3) 2012-02-24 14:05 i686 Cygwin
everything works fine, too.

I already tried a rebaseall without success.

Any idea what could cause this behavior?

Both systems run Windows Server 2008 R2 Datacenter btw.

Regards,
Andre

*http://nant.sourceforge.net/


--
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

Re: [1.7.13] STATUS_ACCESS_VIOLATION when running cygwin programs in NAnt scripts

[Christopher Faylor]

On Sat, Apr 07, 2012 at 10:48:09AM +0200, Andre Loker wrote:
>Hello,
>
>On a new system with a clean 1.7.13 installation (CYGWIN_NT-6.1-WOW64 
>rs200313 1.7.13(0.260/5/3) 2012-04-05 12:43 i686 Cygwin) I'm getting 
>STATUS_ACCESS_VIOLATIONs whenever I try to run any cygwin program as 
>part of a NAnt* build script.
>
>E.g. if I try to execute:
>c:\cygwin\bin\bash.exe --login /cygdrive/c/Backup/syncvia.sh
>
>I get
>
>      [exec] C:\Backup>c:\cygwin\bin\bash.exe --login 
>/cygdrive/c/Backup/syncvia.sh
>      [exec]       0 [main] bash 3468 exception::handle: Exception: 
>STATUS_ACCESS_VIOLATION
>      [exec]     774 [main] bash 3468 open_stackdumpfile: Dumping stack 
>trace to bash.exe.stackdump
>
>Here's the stackdump file:
>Exception: STATUS_ACCESS_VIOLATION at eip=61029E40
>eax=00000000 ebx=0028ABCC ecx=20000668 edx=61188348 esi=00000000 
>edi=00010000
>ebp=00000000 esp=0028AB40 program=c:\cygwin\bin\bash.exe, pid 3732, 
>thread main
>cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B
>Stack trace:
>Frame     Function  Args
>End of stack trace
>
>I have tried to execute other cygwin programs with similar results.
>
>However, if I run the cygwin programs from a cmd prompt or in a shell 
>everything works fine.
>Also, on another machine that uses the same script but runs
>CYGWIN_NT-6.1-WOW64 CT50796 1.7.11(0.260/5/3) 2012-02-24 14:05 i686 Cygwin
>everything works fine, too.
>
>I already tried a rebaseall without success.
>
>Any idea what could cause this behavior?

I have a vague idea.  Try the 2012-04-07 snapshot when it shows up.

http://cygwin.com/snapshots/

cgf

--
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

Re: [1.7.13] STATUS_ACCESS_VIOLATION when running cygwin programs in NAnt scripts

[Andre Loker]

Am 07.04.2012 19:38, schrieb Christopher Faylor:
> On Sat, Apr 07, 2012 at 10:48:09AM +0200, Andre Loker wrote:
>> Hello,
>>
>> On a new system with a clean 1.7.13 installation (CYGWIN_NT-6.1-WOW64
>> rs200313 1.7.13(0.260/5/3) 2012-04-05 12:43 i686 Cygwin) I'm getting
>> STATUS_ACCESS_VIOLATIONs whenever I try to run any cygwin program as
>> part of a NAnt* build script.
>>
> I have a vague idea.  Try the 2012-04-07 snapshot when it shows up.
>
> http://cygwin.com/snapshots/
I tried the snapshot and it works. Thanks a lot for the quick solution! 
I feared my error description was a bit too vague to begin with.

Out of interest - how comes that the error only occurred when the 
programs were run from the build script.

Regards,
Andre


--
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

Re: [1.7.13] STATUS_ACCESS_VIOLATION when running cygwin programs in NAnt scripts

[Christopher Faylor]

On Sat, Apr 07, 2012 at 09:49:24PM +0200, Andre Loker wrote:
>Am 07.04.2012 19:38, schrieb Christopher Faylor:
>> On Sat, Apr 07, 2012 at 10:48:09AM +0200, Andre Loker wrote:
>>> Hello,
>>>
>>> On a new system with a clean 1.7.13 installation (CYGWIN_NT-6.1-WOW64
>>> rs200313 1.7.13(0.260/5/3) 2012-04-05 12:43 i686 Cygwin) I'm getting
>>> STATUS_ACCESS_VIOLATIONs whenever I try to run any cygwin program as
>>> part of a NAnt* build script.
>>>
>> I have a vague idea.  Try the 2012-04-07 snapshot when it shows up.
>>
>> http://cygwin.com/snapshots/
>I tried the snapshot and it works. Thanks a lot for the quick solution! 
>I feared my error description was a bit too vague to begin with.
>
>Out of interest - how comes that the error only occurred when the 
>programs were run from the build script.

I can only guess but I suspect that something was closing stdin/stdout
and we didn't deal correctly with that.

cgf

--
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