This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Bash wait indefinitely

Unfortunately, I don't have any system with more than one CPU, so there's no
way I can test it on a system like that and I have not run into any similar
problems on any of the systems I have.. (Cygwin or otherwise).

I'm afraid someone else will have to debug this, as I don't see that I can
do anything - especially if it's hard to debug, only happens on multi-CPU
systems and only with complex Bash scripts..



On Fri, Nov 28, 2003 at 03:13:45PM -0500, Nicholas Wourms wrote:
> wrote:
> >I'm running in concurrences 5 complex bash batch, and sometimes (2 times on
> >3) one or more (very rarely) batch stop to do something. I've put a lot of
> >trace to see where is the problem, but seems rarely arrived at the same 
> >line
> >of code.
> >
> >I've also tried to use strace tool, but strace hang rapidly.
> >
> For the last few weeks I've been experiencing the same, and the 
> offenders always seem to be either bash (not ash) or make.  It is 
> important to note that I track cygwin's CVS head, so I had chalked it up 
> to the on-going signal work.  I've found that running deep `make`s or 
> running the autotools in succession (such as in the case of triggering 
> the AM_MAINTAINER_MODE routines) often triggers this problem for me on 
> my Dual Athlon MP 2400+ Win2K box :-(.  I've been extremely busy working 
> on other things, I just grumble, kill the deadlocked process and its 
> children, then restart the parent.  Attempting to debug gdb/strace, as 
> you've discovered, is quite fruitless.
> Cheers,
> Nicholas
> --
> Unsubscribe info:
> Problem reports:
> Documentation:
> FAQ:         


Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]