Eric Blake wrote:
> Are you running any sort of background program (virus scanner or
> desktop search engine) that might be interfering with cygwin, so that
> cygwin runs
> out of available Windows processes sooner? What does 'ps -eaf' show,
> when run from another console while your strace is run
On Aug 9 06:56, Eric Blake wrote:
> though, since my trial run has not crashed after more than 30 minutes of
> execution as I type this.
I'm running this test for 3 hours now, no crash.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Cary Jamison on 8/8/2005 6:12 PM:
> Here's the trace from the last twenty seconds of the following command :
>
>strace -t bash test.sh | tee strace.out
>
> where test.sh is simply :
>
>while true ; do sleep 10 ; done
>
> it die
Eric Blake wrote:
> The collected strace would be huge, but may be the next step. Try and
> pick out the tail end of the trace where the crash actually happens,
> rather than the entire trace. But that will only point out what
> syscalls were being made prior to the crash.
Here's the trace from
Eric Blake wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> According to Cary Jamison on 8/5/2005 6:40 PM:
cd $LDIR
while true
do
sleep 10
>>
>>
>> It appears to be crashing here in the sleep. It will go for just a
>> few loops around to several minutes before cras
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Cary Jamison on 8/5/2005 6:40 PM:
>>>cd $LDIR
>>>while true
>>>do
>>> sleep 10
>
>
> It appears to be crashing here in the sleep. It will go for just a few
> loops around to several minutes before crashing.
> What should I try next.
Cary Jamison wrote:
>> Ok, I should have sent it too. There is probably a better way to do
>> this, but here it is...
>>
>> #!/bin/bash
>>
>> # scp anything in the sync directory to the remote machine
>> # and then move it to the done directory.
>> # Currently only works with single files, not dir
Cary Jamison wrote:
> I just ran setup again (the latest version) to get 3.0-11, and made
> sure everything was stopped first. I've now got a proper sh. I'll
> run my script for a while again to see if it still has problems.
It's still crashing, so I'll look at narrowing it down more now...
Car
Eric Blake wrote:
> According to Cary Jamison on 8/4/2005 11:07 AM:
>> Not Found: sh
>> Found: C:\cygwin\bin\tar.exe
>
> Not good. You need /bin/sh to do lots of things in cygwin. Rerun
> setup.exe, and that should help. Perhaps the core dump is happening
> when something is trying to invoke /bi
On Thu, 4 Aug 2005, Eric Blake wrote:
> According to Cary Jamison on 8/4/2005 11:07 AM:
> > Anyway, here are some parts you may care about :
> >
> > cygwin dll 1.5.18
> > bash 3.0-8
> ...
> > Not Found: sh
> > Found: C:\cygwin\bin\tar.exe
>
> Not good. You need /bin/sh to do lots of things in cyg
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Cary Jamison on 8/4/2005 11:07 AM:
> Ok, I should have sent it too. There is probably a better way to do
> this, but here it is...
>
> #!/bin/bash
>
> # scp anything in the sync directory to the remote machine
> # and then move it to th
Eric Blake wrote:
I have a simple script I sometimes run that monitors a directory for any
files dumped in it (sleeps 10 seconds, processes any new files, and loops
around). Since upgrading this script is causing bash to crash. It doesn't
happen immediately, so I'm not sure where exactly in m
> I have a simple script I sometimes run that monitors a directory for any
> files dumped in it (sleeps 10 seconds, processes any new files, and loops
> around). Since upgrading this script is causing bash to crash. It doesn't
> happen immediately, so I'm not sure where exactly in my script th
I recently upgraded an older installation (see attached cygcheck).
I have a simple script I sometimes run that monitors a directory for any
files dumped in it (sleeps 10 seconds, processes any new files, and loops
around). Since upgrading this script is causing bash to crash. It doesn't
happe
14 matches
Mail list logo
