X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: postinstall hang Date: Tue, 1 Apr 2008 11:52:33 -0400 Message-ID: References: <001901c89348$cd86c8b0$06bca8c0@bigtower> <47F19881.2080508@byu.net> <00b001c89400$e59d20d0$2708a8c0@CAM.ARTIMI.COM> From: "Popper, Samuel \(US SSA\)" To: X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id m31Fr5KS021390 > > Is there anything else that could contribute to BLODA? > > Yes, absolutely anything that hooks or injects into processes. Try > using > procexp to get a list of DLLs from the stuck bash processes, and let us > know > what's there. Here's my list of candidate BLODA .dll's from procexp: AcLua.DLL ADVAPI32.DLL apphelp.dll bash.exe CRYPT32.dll ctype.nls cygiconv-2.dll cygintl-8.dll cygncurses-8.dll cygreadline6.dll cygwin1.dll GDI32.dll imagehlp.dll IMM32.DLL kernel32.dll locale.nls MSASN1.dll msvcrt.dll ntdll.dll ole32.dll psapi.dll RPCRT4.dll Secur32.dll sfc_os.dll ShimEng.dll sortkey.nls sorttbls.nls tsappcmp.dll unicode.nls USER32.dll USERENV.dll WINTRUST.dll They all appear to be from cygwin or right from Windows (I can send the desciption/version number information if desired). In case it is relevant, this system is running Server 2003 on a dual-core Pentium D. -Sam -- 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/