Re: BLODA diagnostics
This is exactly what I was looking for, thanks! Looks like the problem was wxvault.dll by Wave Systems. Baldur On Sun, Aug 29, 2010 at 09:28:07PM +0100, Dave Korn wrote: > On 27/08/2010 21:44, mike marchywka wrote: > > On 8/27/10, Baldur Gislason wrote: > > >> Hi, what tool is best to track down what BLODA is causing fork failures on > >> my Cygwin installation? > > > There may be a sysinternals tool, I use those to track down open handles > > that have been a problem on earlier systems. > > Sysinternals Process Explorer has a mode when it shows you all the DLLs > loaded into a process. Any of these that come from security software or other > installed applications (i.e. aren't part of the standard windows system DLLs) > can give you a clue as to what's causing the BLODA. > > If that doesn't help, rebaseall might get things going again, if you haven't > already tried it. (See /usr/share/doc/Cygwin/rebase-3.0.1.README for usage.) > > cheers, > DaveK > > > -- > 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: BLODA diagnostics
I am attempting to diagnose why fork() fails during the cygwin installation. It looks like some kind of BLODA may be causing this, per documentation, but obviously, the list of known troublemakers in the documentation does not cover all troublemakers and I'd like to trace what is going on. Baldur On Fri, Aug 27, 2010 at 04:44:22PM -0400, mike marchywka wrote: > Since no one replied, perhaps you could supply more details. > What exactly are you trying to do and what happens? > > There may be a sysinternals tool, I use those to track down open handles > that have been a problem on earlier systems. > > > On 8/27/10, Baldur Gislason wrote: > > Hi, what tool is best to track down what BLODA is causing fork failures on > > my > > Cygwin installation? > > > > Baldur > > > > -- > > 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 > > > > > > > -- > marchy...@gmail.com > note new address 2009-12-16: > Mike Marchywka > 1975 Village Round > Marietta GA 30064 > 415-264-8477 (w)<- use this > 404-788-1216 (C)<- leave message > 989-348-4796 (P)<- emergency only > marchy...@hotmail.com > Note: If I am asking for free stuff, I normally use for hobby/non-profit > information but may use in investment forums, public and private. > Please indicate any concerns if applicable. > Note: hotmail is censoring incoming mail using random criteria beyond > my control and often hangs my browser > but all my subscriptions are here..., try also marchy...@yahoo.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 > -- 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
BLODA diagnostics
Hi, what tool is best to track down what BLODA is causing fork failures on my Cygwin installation? Baldur -- 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
Cygwin 1.7 problems on Windows XP SP2
Hi, I recently installed the latest version of cygwin after using previous (1.5) versions without problems. Almost nothing works on 1.7 and even after reinstalling my machine I still have the same problem. My machine runs Windows XP SP2. My install.log.full has a lot of errors like this one: 3879146 [main] bash 3716 fork: child -1 - died waiting for longjmp before initialization, retry 0, exit code 0x100, errno 11 4 [main] bash 3872 C:\cygwin\bin\bash.exe: *** fatal error - couldn't allocate heap, Win32 error 487, base 0x6D, top 0x74, reserve_size 454656, allocsize 458752, page_const 4096 This doesn't only happen with bash, it was also happening with other apps such as rsync before I reinstalled the operating system. Any ideas or hints for diagnosing this? Can I acquire an older setup.exe and try installing a previous version of cygwin? Full log is at http://foo.is/~baldur/setup.log.full.gz Baldur -- 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
