From: Kris Thielemans <kris.thielemans@gm...>  20140820 22:06:56

[apologies. ignore previous email. It got sent too early] Hi I've fixed a problem in the Makefiles that "mex o" is no longer supported and replaced it with "mex output". I've also improved the matlabrun command to no longer warn about outdated try/catch syntax. However, I have a problem that I don't know how to solve. For some runtime tests (at this point for instance the overload_simple test with R2012a), currently matlab still crashes because of an error in the mex file. I then get at the end of the output  Attempt to restart MATLAB? [y or n]>>  and the make process hangs. I can only get out of this by pressing CtrlZ and kill 9 the matlab process. Obviously, at some point the tests won't crash anymore, but this behaviour is not acceptable. Even weirder, with R2014a, this crash happens for every test! However, if I run the test by hand, it works:  kris@...:~/devel/swig/build/Examples/testsuite/matlab$ /opt/MATLAB/R2014a/bin/matlab nojvm nodisplay nosplash r "try;import abstract_access.*;;d = abstract_access.D();catch err, fprintf(2,['ERROR: ' err.message '']),exit(1), end, exit(0);" < M A T L A B (R) > Copyright 19842014 The MathWorks, Inc. R2014a (8.3.0.532) 64bit (glnxa64) February 11, 2014 To get started, type one of these: helpwin, helpdesk, or demo. For product information, visit http://www.mathworks.com. kris@...:~/devel/swig/build/Examples/testsuite/matlab$ echo $? 0  As a check, I put that exact statement in a Makefile as a target test, and run that as "make test", then matlab crashes and asks the "restart" question and make hangs. Any ideas? Kris 