Re: OBJDUMP.EXE fails to start

I used cygwin1.dll from cygwin1-20060718.dll.bz2. The problem with OBJDUMP.EXE appears to be fixed. Thank you. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ:

OBJDUMP.EXE fails to start

>From a fresh, new cygwin installation, OBJDUMP.EXE exhibits an intermittent failure. It terminates prematurely. There is no stack dump. Under GDB, the program runs normally. This problem occurs with cygwin 1.5.20-1. The previous version, 1.5.19-4, does not exhibit this behavior. cygcheck.out

Re: slow handling of large sets of files?

On Tue, 2005-02-01 at 14:51 -0500, Larry Hall wrote: > At 02:28 PM 2/1/2005, you wrote: > >I too have been seeing a problem with very slow file access in large > >directories. > > > >Specifically, > > > >On a Cygwin/Win2k box, I have a mirror of an FTP site. The site has 2.5 > >million files sprea

Re: slow handling of large sets of files?

I too have been seeing a problem with very slow file access in large directories. Specifically, On a Cygwin/Win2k box, I have a mirror of an FTP site. The site has 2.5 million files spread between 100 directories. (20,000 - 30,000 files per directory) I have previously run this number of file

RE: Strange Crond behavior

I believe the root cause is that the CYGWIN environment variable needs to be set to include NTSEC. The instructions in /usr/doc/Cygwin/cron.README include this command: cygrunsrv -I cron -p /usr/sbin/cron -a -D That will not always work A command that works better is: cygrunsrv -I cron -d "Cro