[Wien] MIXER runtime error + solution on Mac OS X

[Martin Kroeker]

This might warrant closer scrutiny - was it reproducible with any odd
tutorial problem, or does it require a particular case or type of
calculation ?
The "illegal instruction" abort signals that data was somehow spilling
over into the memory ranges holding the executable code. Now I would not
expect a "simple" heap-stack-collision (from an array that is simply too
big to put on the stack with impunity) to occur on any modern system
except perhaps severely constrained embedded ones. At worst, the abort
should have been accompanied by a "segmentation fault" message as the
attempt to overwrite the running program got caught. So other possible
explanations could be that the code tries to store more array elements
than the array was designed to hold, or that the indexes into the array
are miscalculated (overflowing or not clamped to positive values).
Moving data to the heap may have just changed the location of the 
inadvertently overwritten memory to ranges where the effects are more
subtle (unrelated data) or not noticable (lucky hit on unused memory).
-- 
Dr. Martin Kroeker            martin at ruby.chemie.uni-freiburg.de
c/o Prof.Dr. Caroline Roehr
Institut fuer Anorganische und Analytische Chemie der Universitaet Freiburg