You are here

Unable to compile and cannot reopen the file.

I'm using 64bit5.9 - I had reached a point in my modeling effort where I had wanted to compile the model.  I hade been working on it for a couple of days and had saved it several times including today. When I hit ht ecompile button a messages came up after a bit saying that the prolog was overextended or something of that nature.  Before I could get more details the screen went blank.  When I try to reopen the file sends a message that it cannot find some script and when i hit OK it trys to convert the 64bit 5.9 file from 5.0. Like it thinks it is 5.0.

Reporter: 
John E. Rogers04
Created: 
Tue, 07/02/2012 - 21:37
Updated: 
Fri, 09/03/2012 - 07:12

Comments

Hi John

Could you send a copy of the model that is giving these problems to support@simulistics.com

I will try to find out why it fails to compile. If it is very large perhaps you could zip it first.

Unfortunately I saved another file over it but that file will not open either.  What appered on the screen when i tried to open the file immediately after the sudden shut down was the following.

Possible error:trailstack overflow (size 196608Kb,reached: -87186 Kb-fixed size)

Posible error: cstr stack overflow (size 16384 Kb, reached: -8410245 Kb - fixed size)

Possible error: global stack overflow (size:524288 KB,reached:-296075 Kb - fixed size)

Possible error: local stack overflow (size:262144 Kb, reached: -779712 Kb - fixed size)

 

We think that the opening is trying to find a paramerter that may not exist (or confused) and fell into an infinite loop.

I am currently reconstructing the model from the version I started with a couple of days ago.  I'll let you know how this one works.

These error messages are coming from the Prolog engine which deals with the logic of the model. Parameters are only loaded at model execution time and this is done in the scripting language TclTk. So the problem is in the logic of the saved model. If you send me the model that isn't opening, I might be able to work out how it got corrupted, and figure out at least how to get Simile to load it without falling into an infinite loop.