public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Parzival Herzog" <parz@videon.wave.ca>
To: <cygwin@sourceware.cygnus.com>
Subject: Compiling PM3 Modula-3, worked under B20.0, now hangs "rm", "as", others in infinite loop on B20.1
Date: Thu, 11 Mar 1999 11:54:00 -0000	[thread overview]
Message-ID: <001501be6bf8$84974480$e8e0a1cf@mork.mbnet.mb.ca> (raw)

....I set this message earlier, but it arrived without a message body, so
here it is again!....

I had used B17 - B19 with no problems for months, Then before I installed
PM3 Modula-3,
I updated to B20.0. PM3 Modula-3 ( http://polymtl.ca/m3 ) installed and ran
successfully,
then I updated to B20.1. PM3 Modula-3 and Cygwin appeared to work fine. Then
I tried
to compile a large Modula-3 package, and after compiling part-way through
the
system, my computer hung in an infinite loop, steadily allocating about
50-60K of
memory per second, with 100% CPU utilization, and no significant disk
activity. At first
I thought this was a Modula-3 problem, but gradually started to suspect it
was a timing
problem in the Cygwin library. I noticed that the hang occurred after
approximately the
same amount of elapsed time compiling, and not on the same source file, and
with
exactly the same behaviour while several different programs were active,
i.e. M3cgc1 (the Modula
3 compiler), as (the GNU assembler - called by the compiler), and even once
in "rm" (the Cygwin
rm program, called by make.)

So, I decided to rebuild from scratch the Modula-3 compiler. This failed in
exactly the
same way, with a hang, not always on the same source file, but after roughly
the
same amount of elapsed time well into a (very complex) build process. I then
uninstalled B20.1, and I went to fetch B20.0, but it was gone from the ftp
sites.
(I  guess the "serious bug" fixed in 20.1 caused its withdrawal.) So I
fetched and
re-installed B19.1 Now, Modula-3 installed and ran correctly, and all the
systems
that failed to compile under B20.1, compiled correctly.

Unfortunately, I can't boil this down to a simple isolated case: its not a
specific
program that hangs, but an arbitrary program, and that program is spawned by
a (make-like) shell (m3build) executing a complex build operation. To
reproduce
the problem you have to install PM3 Modula-3. And in order to do that you
need
LOTS of disk space (about 400 MB) and you need a patch (at least for the
PM3 1.1.10 version - this may be fixed in the PM3 1.1.11 release - please
contact michel.dagenais@polymtl.ca  . I can say that PM3 Modula-3 is very
reliable very portable software that installs and works on dozens of
machines and
flavours of UNIX, and I hope the Cygnus developers will look into this
problem relatively
quickly, because it seems that a bug has been introduced or unmasked in
moving
form B20.0 to B20.1.

I have a Windows NT 4.0 system, service pack 4, on a 128MB AMD K6-266
machine,
I run the NTFS file system, with compression turned on.


Parzival


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

WARNING: multiple messages have this Message-ID
From: "Parzival Herzog" <parz@videon.wave.ca>
To: <cygwin@sourceware.cygnus.com>
Subject: Compiling PM3 Modula-3, worked under B20.0, now hangs "rm", "as", others in infinite loop on B20.1
Date: Wed, 31 Mar 1999 19:45:00 -0000	[thread overview]
Message-ID: <001501be6bf8$84974480$e8e0a1cf@mork.mbnet.mb.ca> (raw)
Message-ID: <19990331194500.vGIyg8q20KixyoOTTzc7E6E407Do1ttXgSBT9SYbry4@z> (raw)

....I set this message earlier, but it arrived without a message body, so
here it is again!....

I had used B17 - B19 with no problems for months, Then before I installed
PM3 Modula-3,
I updated to B20.0. PM3 Modula-3 ( http://polymtl.ca/m3 ) installed and ran
successfully,
then I updated to B20.1. PM3 Modula-3 and Cygwin appeared to work fine. Then
I tried
to compile a large Modula-3 package, and after compiling part-way through
the
system, my computer hung in an infinite loop, steadily allocating about
50-60K of
memory per second, with 100% CPU utilization, and no significant disk
activity. At first
I thought this was a Modula-3 problem, but gradually started to suspect it
was a timing
problem in the Cygwin library. I noticed that the hang occurred after
approximately the
same amount of elapsed time compiling, and not on the same source file, and
with
exactly the same behaviour while several different programs were active,
i.e. M3cgc1 (the Modula
3 compiler), as (the GNU assembler - called by the compiler), and even once
in "rm" (the Cygwin
rm program, called by make.)

So, I decided to rebuild from scratch the Modula-3 compiler. This failed in
exactly the
same way, with a hang, not always on the same source file, but after roughly
the
same amount of elapsed time well into a (very complex) build process. I then
uninstalled B20.1, and I went to fetch B20.0, but it was gone from the ftp
sites.
(I  guess the "serious bug" fixed in 20.1 caused its withdrawal.) So I
fetched and
re-installed B19.1 Now, Modula-3 installed and ran correctly, and all the
systems
that failed to compile under B20.1, compiled correctly.

Unfortunately, I can't boil this down to a simple isolated case: its not a
specific
program that hangs, but an arbitrary program, and that program is spawned by
a (make-like) shell (m3build) executing a complex build operation. To
reproduce
the problem you have to install PM3 Modula-3. And in order to do that you
need
LOTS of disk space (about 400 MB) and you need a patch (at least for the
PM3 1.1.10 version - this may be fixed in the PM3 1.1.11 release - please
contact michel.dagenais@polymtl.ca  . I can say that PM3 Modula-3 is very
reliable very portable software that installs and works on dozens of
machines and
flavours of UNIX, and I hope the Cygnus developers will look into this
problem relatively
quickly, because it seems that a bug has been introduced or unmasked in
moving
form B20.0 to B20.1.

I have a Windows NT 4.0 system, service pack 4, on a 128MB AMD K6-266
machine,
I run the NTFS file system, with compression turned on.


Parzival


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com


             reply	other threads:[~1999-03-11 11:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-11 11:54 Parzival Herzog [this message]
1999-03-31 19:45 ` Parzival Herzog
  -- strict thread matches above, loose matches on Subject: below --
1999-12-29 13:30 John Polstra
1999-12-31 13:28 ` John Polstra
1999-03-08 23:02 Parzival Herzog
1999-03-31 19:45 ` Parzival Herzog

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='001501be6bf8$84974480$e8e0a1cf@mork.mbnet.mb.ca' \
    --to=parz@videon.wave.ca \
    --cc=cygwin@sourceware.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).