Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!rex!uflorida!gatech!ncsuvx!ece-csc!ncrcae!hubcap!fenrich
From: fenrich@cs.buffalo.edu (Rick Fenrich)
Newsgroups: comp.parallel
Subject: Problems with Intel iPSC/2?
Message-ID: <5095@hubcap.clemson.edu>
Date: 12 Apr 89 18:34:29 GMT
Sender: fpst@hubcap.clemson.edu
Lines: 24
Approved: parallel@hubcap.clemson.edu

I have been writing some programs on the Intel iPSC/2 with C using
dynamic memory allocation. My problem is that when I run the program
it seems to run fine and then it hangs, giving no output nor releasing
the cube. A friend of mine has had the same problem with dynamic
memory allocation. We know it is not a synchronization problem and it
is not a looping problem. Has anyone out there come across similar
problems and if so what was your approach to a solution? By the way,
my friend said his program works once he removes "free(pointer)" to
free up allocated storage.

Another problem that we have been having is that when we run a job in
the foreground and we need to cancel it we use Ctrl-C. Sometimes when
Ctrl-C is hit more than once the nodes become inoperable. We get messages
such as "cubetype not found", etc. One solution is to background the
job and then kill it, but if we use debug statements we will not be
able to retrieve the last lines of output since output is buffered.
Any suggestions on how to avoid the Ctrl-C problem?

I appreciate any help you can give!!

						Rick Fenrich

						fenrich@cs.buffalo.edu
						fenrich@sunybcs.bitnet