Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Sat, 4 Oct 2003 13:40:24 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: cygpath hangs from postinstall scripts when called like $(cygpath -S) but not otherwise Message-ID: <20031004174024.GC31073@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <1065241514 DOT 18546 DOT 19 DOT camel AT localhost> <00dd01c38a7b$fbfc91f0$12760251 AT ximenes> <019501c38a95$71f11110$12760251 AT ximenes> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <019501c38a95$71f11110$12760251@ximenes> User-Agent: Mutt/1.4.1i On Sat, Oct 04, 2003 at 05:34:55PM +0100, Cliff Hones wrote: >Cliff Hones wrote: >> ... >> I suspect you will see something different. I guess if on some Windows >> systems shlwapi.dll has a dependence on msvcrt.dll, it is not safe >> to call this from any cygwin app. > >I think this may have been introduced with W2k SP4. I found the following >version of shlwapi.dll on my system: > >$ ls -l /d/winnt/servicepackfiles/i386/shlwapi.dll >-rwx------+ 1 Administ None 289552 Jun 19 12:05 >/d/winnt/servicepackfiles/i386/shlwapi.dll > >$ cygcheck /d/winnt/servicepackfiles/i386/shlwapi.dll >D:/winnt/servicepackfiles/i386/shlwapi.dll > D:/winnt/servicepackfiles/i386\GDI32.DLL > D:/winnt/servicepackfiles/i386\NTDLL.DLL > D:/winnt/servicepackfiles/i386\KERNEL32.DLL > D:/winnt/servicepackfiles/i386\USER32.DLL > D:/winnt/servicepackfiles/i386\ADVAPI32.DLL > D:/winnt/servicepackfiles/i386\RPCRT4.DLL > >and there is no msvcrt dependence with this earlier version. > >Does this fit with the hanging symptoms? i.e. if your postinstall >hangs, have you installed W2K SP4, or is your shlwapi dependent on >msvcrt, or is this just a red herring? I'm not paying much attention to this thread but it sure seems like everyone is treating this like a situation for debugging a closed source application where you have to guess rather then investigate source code. Has anyone tried building a debugging version of cygpath and attaching to it with gdb when it hangs? Or, alternatively attaching to the shell which invoked the cygpath? -- 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/