PPPP wrote:
>
>
> Thanks Larry. I ran your command and I was able to strace something.
> Here is the output of the strace:
>
> --- Process 1052, exception C0000005 at 610610C5
> --- Process 3572, exception 000006BA at 76A8F35F
> --- Process 3572, exception 000006BA at 76A8F35F
> --- Process 3572, exception 000006BA at 76A8F35F
> --- Process 3572, exception 000006BA at 76A8F35F
> --- Process 3572, exception 000006BA at 76A8F35F
> --- Process 3572, exception 000006BA at 76A8F35F
> --- Process 3572, exception 000006BA at 76A8F35F
> --- Process 3572, exception 000006BA at 76A8F35F
> --- Process 3572, exception 000006BA at 76A8F35F
> --- Process 3572, exception 000006BA at 76A8F35F
> --- Process 3572, exception 000006BA at 76A8F35F
> --- Process 3572, exception 000006BA at 76A8F35F
> --- Process 3572, exception 000006BA at 76A8F35F
> --- Process 3572, exception 000006BA at 76A8F35F
> --- Process 3572, exception C0000005 at 004096B6
>
> Which isn't very useful...how should I tackle this?
>
I got more in the DOS window:
Memory Problem, can't allocate memory
0 0 [main] paAgent.exe 1025 handle_exceptions: Exception:
STATUS_ACCESS_VIOLATION
0 500 [main] paAgent 1025 handle_exceptions: Dumping stack trace to
paAgent.exe.core
0 0 [main] paAgent.exe 1023 sync_with_child: child 3252(0x178)
died before initialization with status code 0
0 384 [main] paAgent 1023 sync_with_child: *** child state waiting
for longjmp
14873272 14873656 [main] paAgent 1023 handle_exceptions: Exception:
STATUS_ACCESS_VIOLATION
595 14874251 [main] paAgent 1023 handle_exceptions: Dumping stack trace to
paAgent.exe.core
--
View this message in context:
http://www.nabble.com/Application-causes-STATUS_ACCESS_VIOLATION-in-Windows-2008-tp20843624p20861151.html
Sent from the Cygwin list mailing list archive at Nabble.com.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/