From: Tadeusz Liszka <tad@comco.com>
To: Greg Miller <gmiller@classic-games.com>
Cc: gnu-win32@cygnus.com
Subject: Re: Help: Make going wild
Date: Wed, 03 Feb 1999 12:28:00 -0000 [thread overview]
Message-ID: <36B8B117.741018C1@comco.com> (raw)
In-Reply-To: <36B76458.37BBA093@classic-games.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
WARNING: multiple messages have this Message-ID
From: Tadeusz Liszka <tad@comco.com>
To: Greg Miller <gmiller@classic-games.com>
Cc: gnu-win32@cygnus.com
Subject: Re: Help: Make going wild
Date: Sun, 28 Feb 1999 23:02:00 -0000 [thread overview]
Message-ID: <36B8B117.741018C1@comco.com> (raw)
Message-ID: <19990228230200.qULoebUNPFO1Myi4djDrmoF_GOar2hN80Y2xfNGNUKQ@z> (raw)
In-Reply-To: <36B76458.37BBA093@classic-games.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
next prev parent reply other threads:[~1999-02-03 12:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-02 10:10 Tadeusz Liszka
1999-02-02 11:42 ` Tadeusz Liszka
[not found] ` < 36B75504.4A553F4C@comco.com >
1999-02-02 12:15 ` Geoffrey Noer
1999-02-28 23:02 ` Geoffrey Noer
1999-02-02 12:47 ` Greg Miller
1999-02-03 12:28 ` Tadeusz Liszka [this message]
1999-02-28 23:02 ` Tadeusz Liszka
1999-02-28 23:02 ` Greg Miller
1999-02-28 23:02 ` Tadeusz Liszka
1999-02-28 23:02 ` Tadeusz Liszka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=36B8B117.741018C1@comco.com \
--to=tad@comco.com \
--cc=gmiller@classic-games.com \
--cc=gnu-win32@cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).