Michael Jones (mtj++at++babar)
Thu, 28 Mar 1996 07:29:04 -0800
First, making a directory named "core" in the directory where you execute
your application will get you out of the "my core file is too big" state.
More importantly, though, is this -- I don't know of any case where MP on
an Indy, Indigo2, Crimson, RealityStation, or iStation has a problem not
seen on a multiprocessor system. I'll accept that there are certain very
minor differences (e.g. when running as root and isolating CPU's, IRIX will
ignore the request to isolate CPU 0, etc.). Other than that, I expect that
any core-dumping MP on SP situation would be a core dumping MP on MP as
well.
If you or anyone else has had contrary experiences, it would be a major bug,
and I request you to let us know about it ASAP.
I am not saying that applications can not break when going to MP. I'm only
saying that "simulated" multiprocessing (i.e. multiprogramming) and real
multi-CPU multiprocessing (PowerSeries or Onyx) are not distinguishable in
performer (exept for the minor isolate restriction above, which is harmless).
Michael Jones
Be seeing you, Phone:415.933.1455 Fax:415.965.2658 M/S:8U-590
Michael T. Jones Silicon Graphics, Advanced Systems Division
mtj++at++sgi.com 2011 N. Shoreline Blvd., Mtn. View, CA 94039-7311
"Du musst Amboss oder Hammer sein" -- Goethe
This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:52:36 PDT