Services & Resources / Wolfram Forums
-----
 /
MathGroup Archive
1992
*January
*February
*March
*April
*May
*June
*July
*August
*September
*October
*November
*December
*Archive Index
*Ask about this page
*Print this page
*Give us feedback
*Sign up for the Wolfram Insider

MathGroup Archive 1992

[Date Index] [Thread Index] [Author Index]

Search the Archive

Conflict between Mma and Compact Virtual

  • To: mathgroup at yoda.physics.unc.edu
  • Subject: Conflict between Mma and Compact Virtual
  • From: riddle at mathcs.emory.edu (Larry Riddle)
  • Date: Tue, 18 Aug 92 21:22:52 -0400

Two weeks ago I sent a message to technical support at both
Wolfram Research and Connectix about a conflict I have been
experiencing between Mathematica 2.0 (and 2.1) and Compact Virtual
that results in Mathematica crashing when I quit the program when I am using
virtual memory under the Finder. So far I have received no response
from either company.

I don't expect anyone on this mailing list to tell me how to solve this
problem (thought if you could...) but I am wondering if anyone else has
experienced such problems with a similar hardware setup. More details
are given below if you're interested.

Hardware background:
Macintosh SE with a Mobius 68030 accelerator with 4 megs on the
accelerator and 2.5 megs on the mother board, one-page monitor
Systme 6.07

With this same hardware setup, I had no problems running Mathematica
1.2 using virtual memory with Virtual 2.0. However, when I upgraded to
Mathematica 2.0, the program would crash every time when I quit (but
*usually* not while I was using the program). I then upgraded to Compact 
Virtual 3.0 but Mathematica 2.0 still crashed upon quitting. Just 
recently I upgraded to Mathematica 2.1 which also crashes upon quitting.

Crashes only occur when using the Finder. Under multifinder Mathematica
does not crash using virtual memory (of course, I also do not have
enough memory to do much in Mathematica since under multifinder the
largest unused block is only about 3000K).

Crashes only occur when using virtual memory. If the amount of memory
is set to 4096, so no virtual memory is used and "extended memory" is
unchecked, Mathematical will not crash upon quitting. When the amount
of memory is set to 8192, Mathematical crashes upon quitting.

Here are the messages I get when Mathematical 2.1 crashes upon
quitting. The bomb box alternates between "address error" and "math
coprocessor not installed". I installed SoftwareFPU and then when the
program quits the screen simply freezes with no bomb box.

I installed Macsbug and when Mathematica crashed got the message

undefined A-trap at 007A3382
*MOVEM.L (A7)+,A0/A1

The command sc7 gives the message
Damage stack: A7 must be even and <= CurStackBase

Larry Riddle        | riddle at mathcs.emory.edu         PREFERRED
Agnes Scott College | {rutgers,gatech}!emory!riddle    UUCP 
Dept of Math        | riddle at emory.bitnet             NON-DOMAIN BITNET
Decatur, GA 30030   | (404) 371-6222                  AT&T





  • Prev by Date: Undefined PostScript commands
  • Next by Date: translating the APL 'deal' function into M recursively, procedurally and functionally - one-liners are faster
  • Previous by thread: Undefined PostScript commands
  • Next by thread: translating the APL 'deal' function into M recursively, procedurally and functionally - one-liners are faster