'screen' stackdump very often.

'screen' stackdump very often.

[Oleksandr Gavenko]

Sometimes it started properly but usually not.

   $ screen --version
Screen version 4.00.03 (FAU) 23-Oct-06

   $ screen
       2 [main] screen 2876 exception::handle: Exception: 
STATUS_ACCESS_VIOLATION
    1058 [main] screen 2876 open_stackdumpfile: Dumping stack trace to 
screen.exe.stackdump
       2 [main] screen 3944 exception::handle: Exception: 
STATUS_ACCESS_VIOLATION
   17847 [main] screen 3944 open_stackdumpfile: Dumping stack trace to 
screen.exe.stackdump
       2 [main] screen 3112 exception::handle: Exception: 
STATUS_ACCESS_VIOLATION
    1048 [main] screen 3112 open_stackdumpfile: Dumping stack trace to 
screen.exe.stackdump
     283 [main] screen 3972 exception::handle: Exception: 
STATUS_ACCESS_VIOLATION
   35719 [main] screen 3972 open_stackdumpfile: Dumping stack trace to 
screen.exe.stackdump
       2 [main] screen 3488 exception::handle: Exception: 
STATUS_ACCESS_VIOLATION
   14700 [main] screen 3488 open_stackdumpfile: Dumping stack trace to 
screen.exe.stackdump
       2 [main] screen 3292 exception::handle: Exception: 
STATUS_ACCESS_VIOLATION
     425 [main] screen 3292 open_stackdumpfile: Dumping stack trace to 
screen.exe.stackdump
       2 [main] screen 3484 fork: child -1 - died waiting for longjmp 
before initialization, retry 0, exit code 0x600, errno 11
fork: Resource temporarily unavailable



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