Stackdump at every second startup
Hi guys, I've been experienceing some error messages lately, so I did a fresh resinstall of Cygwin on my Win7-64 machine. All settings left as defaults. I tried alternating Run as Administrator during both setup and when starting Cygwin. That didn't seem to change much. The strange thing is that I get these errors every second time I start Cygwin. I hope there is a fix to this so that the standard installation again works out of the box. Thanks, Borge 0 [main] bash 7500 exception::handle: Exception: STATUS_ACCESS_VIOLATION 488 [main] bash 7500 open_stackdumpfile: Dumping stack trace to bash.exe.stackdump 0 [main] bash 7364 exception::handle: Exception: STATUS_ACCESS_VIOLATION 423 [main] bash 7364 open_stackdumpfile: Dumping stack trace to bash.exe.stackdump 0 [main] -bash 7784 child_copy: linked dll data write copy failed, 0x33E000..0x3425C4, done 0, windows pid 8080, Win32 error 487 -bash: fork: retry: Resource temporarily unavailable borge@QNKTC-1 ~ $ Next startup is clean. The startup following that: 0 [main] bash 8144 exception::handle: Exception: STATUS_ACCESS_VIOLATION 480 [main] bash 8144 open_stackdumpfile: Dumping stack trace to bash.exe.sta ckdump 0 [main] bash 6808 exception::handle: Exception: STATUS_ACCESS_VIOLATION 448 [main] bash 6808 open_stackdumpfile: Dumping stack trace to bash.exe.sta ckdump 0 [main] bash 4632 exception::handle: Exception: STATUS_ACCESS_VIOLATION 413 [main] bash 4632 open_stackdumpfile: Dumping stack trace to bash.exe.sta ckdump 0 [main] bash 7096 exception::handle: Exception: STATUS_ACCESS_VIOLATION 406 [main] bash 7096 open_stackdumpfile: Dumping stack trace to bash.exe.sta ckdump 0 [main] bash 7680 exception::handle: Exception: STATUS_ACCESS_VIOLATION 369 [main] bash 7680 open_stackdumpfile: Dumping stack trace to bash.exe.sta ckdump 0 [main] bash 8104 exception::handle: Exception: STATUS_ACCESS_VIOLATION 466 [main] bash 8104 open_stackdumpfile: Dumping stack trace to bash.exe.sta ckdump 0 [main] -bash 8136 fork: child -1 - died waiting for longjmp before initi alization, retry 0, exit code 0x600, errno 11 -bash: fork: retry: Resource temporarily unavailable 1034721 [main] bash 7772 exception::handle: Exception: STATUS_ACCESS_VIOLATION 1035945 [main] bash 7772 open_stackdumpfile: Dumping stack trace to bash.exe.sta ckdump 1128688 [main] bash 7452 exception::handle: Exception: STATUS_ACCESS_VIOLATION 1129036 [main] bash 7452 open_stackdumpfile: Dumping stack trace to bash.exe.sta ckdump 1248292 [main] -bash 8136 child_copy: linked dll data write copy failed, 0x2CE00 0..0x2D25C4, done 0, windows pid 1420, Win32 error 487 -bash: fork: retry: Resource temporarily unavailable 2270677 [main] bash 6916 exception::handle: Exception: STATUS_ACCESS_VIOLATION 2272002 [main] bash 6916 open_stackdumpfile: Dumping stack trace to bash.exe.sta ckdump 2361092 [main] bash 6368 exception::handle: Exception: STATUS_ACCESS_VIOLATION 2362151 [main] bash 6368 open_stackdumpfile: Dumping stack trace to bash.exe.sta ckdump 2393422 [main] -bash 3380 child_copy: linked dll data write copy failed, 0x2CE00 0..0x2D25C4, done 0, windows pid 3380, Win32 error 487 -bash: fork: retry: Resource temporarily unavailable 3416412 [main] bash 7480 exception::handle: Exception: STATUS_ACCESS_VIOLATION 3417776 [main] bash 7480 open_stackdumpfile: Dumping stack trace to bash.exe.sta ckdump 3451925 [main] bash 7300 exception::handle: Exception: STATUS_ACCESS_VIOLATION 3452480 [main] bash 7300 open_stackdumpfile: Dumping stack trace to bash.exe.sta ckdump 3485149 [main] bash 7336 exception::handle: Exception: STATUS_ACCESS_VIOLATION 3485687 [main] bash 7336 open_stackdumpfile: Dumping stack trace to bash.exe.sta ckdump 3512614 [main] bash 5284 exception::handle: Exception: STATUS_ACCESS_VIOLATION 3512964 [main] bash 5284 open_stackdumpfile: Dumping stack trace to bash.exe.sta ckdump 360 [main] bash 5752 exception::handle: Exception: STATUS_ACCESS_VIOLATION 3604795 [main] bash 5752 open_stackdumpfile: Dumping stack trace to bash.exe.sta ckdump 3679929 [main] bash 4260 exception::handle: Exception: STATUS_ACCESS_VIOLATION 3680351 [main] bash 4260 open_stackdumpfile: Dumping stack trace to bash.exe.sta ckdump 3712398 [main] bash 180 exception::handle: Exception: STATUS_ACCESS_VIOLATION 3712752 [main] bash 180 open_stackdumpfile: Dumping stack trace to bash.exe.stac kdump 3740830 [main] bash 3956
Re: Stackdump at every second startup
On 1/3/2012 7:11 AM, Børge Strand-Bergesen wrote: Hi guys, I've been experienceing some error messages lately, so I did a fresh resinstall of Cygwin on my Win7-64 machine. All settings left as defaults. I tried alternating Run as Administrator during both setup and when starting Cygwin. That didn't seem to change much. The strange thing is that I get these errors every second time I start Cygwin. I hope there is a fix to this so that the standard installation again works out of the box. Thanks, Borge -bash: fork: retry: Resource temporarily unavailable In my experience this generally indicates a need to run rebaseall. It is caused by Windows 7's placement of dlls in the virtual address space; rebaseall gives each cygwin dll a fixed place and insists harder on it. Regards -- EM -- 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: Stackdump at every second startup
Thanks, I hope I used the right syntax in cmd. I ran it as Admin. The result is the same, though, stackdump at every second cygwin startup. Børge Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\borgecd \cygwin\bin C:\cygwin\binash rebaseall rebaseall: 29: cd: can't cd to rebaseall C:\cygwin\binash ./rebaseall C:\cygwin\bin On Tue, Jan 3, 2012 at 13:20, Eliot Moss m...@cs.umass.edu wrote: On 1/3/2012 7:11 AM, Børge Strand-Bergesen wrote: Hi guys, I've been experienceing some error messages lately, so I did a fresh resinstall of Cygwin on my Win7-64 machine. All settings left as defaults. I tried alternating Run as Administrator during both setup and when starting Cygwin. That didn't seem to change much. The strange thing is that I get these errors every second time I start Cygwin. I hope there is a fix to this so that the standard installation again works out of the box. Thanks, Borge -bash: fork: retry: Resource temporarily unavailable In my experience this generally indicates a need to run rebaseall. It is caused by Windows 7's placement of dlls in the virtual address space; rebaseall gives each cygwin dll a fixed place and insists harder on it. Regards -- EM -- 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 -- 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: Stackdump at every second startup
On 1/3/2012 1:29 PM, Børge Strand-Bergesen wrote: Thanks, I hope I used the right syntax in cmd. I ran it as Admin. The result is the same, though, stackdump at every second cygwin startup. Børge Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\borgecd \cygwin\bin C:\cygwin\binash rebaseall rebaseall: 29: cd: can't cd to rebaseall C:\cygwin\binash ./rebaseall C:\cygwin\bin try: chdir c:\cygwin\bin dash -l -i -c rebaseall -- 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: Stackdump at every second startup
That seems to have done the trick. Thanks! Børge On Tue, Jan 3, 2012 at 15:25, marco atzeri marco.atz...@gmail.com wrote: On 1/3/2012 1:29 PM, Børge Strand-Bergesen wrote: Thanks, I hope I used the right syntax in cmd. I ran it as Admin. The result is the same, though, stackdump at every second cygwin startup. Børge Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\borgecd \cygwin\bin C:\cygwin\binash rebaseall rebaseall: 29: cd: can't cd to rebaseall C:\cygwin\binash ./rebaseall C:\cygwin\bin try: chdir c:\cygwin\bin dash -l -i -c rebaseall -- 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 -- 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: Stackdump at every second startup
marco atzeri-4 wrote: C:\cygwin\binash ./rebaseall chdir c:\cygwin\bin dash -l -i -c rebaseall Er... this should not have resulted in anything different from the previous, right? I know there was another failing attempt, but this was already corrected... My real question now: is the need for './peflagsall' in addition gone? Marc -- View this message in context: http://old.nabble.com/Stackdump-at-every-second-startup-tp33071456p33073231.html Sent from the Cygwin list mailing list archive at Nabble.com. -- 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: Stackdump at every second startup
On 1/3/2012 5:58 PM, Marc Girod wrote: marco atzeri-4 wrote: C:\cygwin\binash ./rebaseall chdir c:\cygwin\bin dash -l -i -c rebaseall Er... this should not have resulted in anything different from the previous, right? I guess -c is critical and -l puts a clean cygwin enviroment. I know there was another failing attempt, but this was already corrected... My real question now: is the need for './peflagsall' in addition gone? Marc peflagsall is not usually needed, specially with latest snapshots. Regards Marco -- 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
