First question: are you using any of your own personal modules? A very
typical cause of the problem you describe is bad memory management which
(usually!) comes from new code (e.g. going beyond the bounds of an array)
It is also conceivable that your new data set is flawed in some way.
It is also possible you've found a bug.
Try the following. Put a verify module after import just to make sure that
there's nothing flaky there. Then enable tracing (Message
Window->Commands->Debug Tracing "on"). Now run until you get the problem.
Look in the message window to see what the last module running was. This
(may) be where the problem is occurring (it might possibly also have
occurred earlier, but this is a good start)
Donna L. Gresh, Ph.D.
IBM T.J. Watson Research Center
(914) 945-2472
http://www.research.ibm.com/people/g/donnagresh
[EMAIL PROTECTED]
"Risner, Joel"
<[EMAIL PROTECTED]> To:
"'[email protected]'"
Sent by:
<[email protected]>
[EMAIL PROTECTED] cc:
son.ibm.com Subject:
[opendx-users] Network abort problem
09/24/2002 01:32 PM
Please respond to
opendx-users
I have an OpenDX network which I have used successfully for a period of
several months. I am currently trying to visualize a data set which is
about twice the size of any data sets I have previously used.
While I can sometimes get successful results with this larger data set, I
have also had a number of crashes. I am having trouble trying to determine
what the problem is. I have gotten a variety of messages printed following
these crashes: sometimes "segmentation fault", sometimes "bus error",
sometimes "311724 (or some other integer): signal 11 caught", sometimes
just "killed". Any suggestions on how I should go about determining the
cause of the problem(s)?
Thanks,
Joel Risner
[EMAIL PROTECTED]
