This is the mail archive of the cygwin@sourceware.cygnus.com
mailing list for the Cygwin project. See the Cygwin
home page for more information.
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index] [Subject Index] [Author Index] [Thread Index]
Re: Help: Make going wild
- To: Greg Miller <gmiller@classic-games.com>
- Subject: Re: Help: Make going wild
- From: Tadeusz Liszka <tad@comco.com>
- Date: Wed, 03 Feb 1999 14:27:03 -0600
- CC: gnu-win32@cygnus.com
- Delivered-To: listarch-cygwin@sourceware.cygnus.com
- Delivered-To: mailing list cygwin@sourceware.cygnus.com
- Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
- Organization: Computational Mechanics, Inc.
- References: <36B73F73.C88FB653@comco.com> <36B75504.4A553F4C@comco.com> <36B76458.37BBA093@classic-games.com>
- Sender: tad@comco.com
Thank you very much for the responses to my mail.
I have got two confirmations that the cygwin+NT4sp4 is cool, but
unfortunately I am positive that this is the source of the problem in my
case. Apparently Microsoft investigated CYGNUS and managed to slip some
goodie into sp4 (:-)
So the situation again:
make calls the sh script, which calls dsmake, which uses several exec's
to manipulate files (cat, cp, rm)
Dsmake is our proprietary preprocessor, built using lex/yacc
Initially I compiled dsmake using VC++ (and MKS lex/yacc). This worked
ok in NT4sp3.
When I switched to sp4 (reproduced on at least three different machines)
some of the exec'd Unix functions go wild (take 99%CPU, grow in size
~50K/sec, and never quit). It is random: sometimes it is rm sometimes cp
I have even seen cmd.exe doing it !. Everytime this happens there is
empty line printed to the screen (?)
After recompilation of dsmake using CYGNUS tools (lex/yacc/gcc)
everything so far works as expected.
I see following possible explanations:
1. sp4 changed the exec system call in a way incompatible with CYGWIN
2. dsmake compiled with sp3 will not work with sp4
3. conceivably there could be error in VC++ or MKS lex/yacc, which shows
only after seemingly unrelated sp4 update
4. I ruled out error in dsmake itself (it's been around for a while on
several Unixes, the logic is simple, and has been debugged and purified
carefully), but there may be some lex/yacc non-portable stuff, which
shows on MKS lex/yacc only
I have no resources nor enough CYGNUS experience to investigate error,
if the new recompiled dsmake passes all tests - I will drop the issue.
However option No 1 above is my best bet - as such it may warrant
investigations by somebody. I can reproduce problem and send
nonproprietary part of the code if there is interest.
regards
Greg Miller wrote:
>
> Tadeusz Liszka wrote:
> > Following is from the good, working setup (NT4sp3) and it may not be
> > pertinent to the problem
> >
> > The intermittent error message I was getting sometimes is:
> >
> > proc: c:\cygnus....\make.EXE 1000 (0) sig_send: wait for sig_complete
> > event failed, sig 20, rc -1, error 6
>
> I get this all the time on my setup with NT4sp4, but it occurs after the
> final executable is produced and appears to be harmless. I suspect it's
> unrelated to your main problem.
> --
> http://www.classic-games.com/
> If Bill Clinton doesn't have to obey the law, neither do you.
> *** NEWBIES: Limit signatures to four lines! No HTML mail or posts! ***
--
Tadeusz
:: The public opinion should be alarmed by its own nonexistence
:: (512)467-0618 ext. 526 :: Stanislaw J. Lec, trans. TJL