Octave mingw 3.2.0 crashes

[John W. Eaton]

On 19-Jun-2009, nit_ar wrote:

| Referring to my previous post about octave mingw 3.2.0 crashes, the 
| first two examples are possibly caused by some swig based packages which 
| when loaded, cause octave to crash whenever 'clear functions' is  
| executed. When I have tried to uninstall all packages, this crash (first 
| two examples) doesn't occur anymore.
| 
| However, the crash associated with example C, still happens.
| 
| I have simplified my previous example C test case which cause octave 
| mingw 3.2.0 to crash on my XP SP3 machine:
| 
| The simplified test case is based on the following simple testf2.m 
| function which only evals its input string:
| 
| --------------------
| function testf2(str);
| 
| eval(str);
| --------------------
| 
| When I am calling this function as follows for the first time:
| testf2('testf2(''a=1;'');');
| 
| octave crashes with the following messages (copied from console before 
| closing by windows)
| 
| --------------------
|  > testf2('testf2(''a=1;'');');
| Assertion failed: xcurrent_context == 0, file 
| d:/files/admin/octaveforge_svn/trunk/octave-forge/admin/Windows/mingw32/octave/octave-3.2.0/src/symtab.h, 
| line 1065
| 
| This application has requested the Runtime to terminate it in an unusual 
| way.
| Please contact the application's support team for more information.
| panic: Aborted -- stopping myself...
| attempting to save variables to `octave-core'...
| save to `octave-core' complete
| --------------------
| 
| The octave-core contains only the following string:
| Octave-1-L

The octave-core files is just a copy of your top-level workspace.  If
you didn't create any variables there, then the octave-core file will
be empty.

| When I am splitting the above call into two calls as follows, octave 
| doesn't crash:
| 
| testf2('a=1;');
| testf2('testf2(''a=1;'');');
| 
| 
| I hope that this bug will be resolved since I am using such 'eval' based 
| parameters setting functions in a project which has been run being run 
| with octave MSVC 3.0.3 and now is being run with octave mingw 3.0.5 
| without any problems and I wish to start runing it with recent octave 
| mingw 3.2.0.

This problem seems to be fixed in 3.2.2 and the current development
version.

jwe