From: genew@netcom.com (Gene Wagenbreth) Newsgroups: comp.parallel.mpi Subject: Re: A real puzzler? Date: 16 Jul 1999 20:28:24 GMT Organization: Netcom Message-Id: <7mo4l8$knk@dfw-ixnews8.ix.netcom.com> References: NNTP-Posting-User: genew Xref: ukc comp.parallel.mpi:5347 The best way to diagnose a problem is to shorten your code as much as possible such that the problem still occurs. You ought to be able to post a very small code that exibits the bad behavior. If not, at some point you will find that if you delete a certain statement or group of statements, the problem goes away. The content of that group of statements is a major clue as to what is going on and how to fix it. Sorry if its a pain, but thats why programming is so frustrating. You go to do something straight forward that you think will take a day, and run into a problem that takes 3 days to fix. But you gain information that is useful in the long run. -- ------------------------------------------------------------------- Gene Wagenbreth Programming for Dollars My opinions are mine, I think. -------------------------------------------------------------------