Another example of intermittent shell failure...

[marco atzeri]

On 1/17/2012 5:10 PM, Paul Breslin wrote:
>        0 [main] sh 2272 exception::handle: Exception: STATUS_ACCESS_VIOLATION
>      630 [main] sh 2272 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump
>        0 [main] sh 3392 exception::handle: Exception: STATUS_ACCESS_VIOLATION
>      808 [main] sh 3392 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump
>        0 [main] sh 6388 exception::handle: Exception: STATUS_ACCESS_VIOLATION
>      727 [main] sh 6388 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump
>        0 [main] sh 9316 exception::handle: Exception: STATUS_ACCESS_VIOLATION
>      446 [main] sh 9316 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump
>        0 [main] sh 1872 exception::handle: Exception: STATUS_ACCESS_VIOLATION
>      851 [main] sh 1872 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump
>        0 [main] sh 9160 exception::handle: Exception: STATUS_ACCESS_VIOLATION
>      424 [main] sh 9160 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump
>        0 [main] sh 3784 fork: child -1 - died waiting for longjmp before initialization, retry 0, exit code 0x600, errno 11
> /bin/sh: fork: retry: Resource temporarily unavailable

fork issues are usually solved with rebaseall,
additionally you can also try a recent snapshots

http://cygwin.com/snapshots/


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