Matlab crashes but Octave doesn't

3 次查看（过去 30 天）

Douglas Brenner 2019-1-2

0
链接

此问题的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/437894-matlab-crashes-but-octave-doesn-t

回答： Douglas Brenner 2019-1-2

The program below runs in Octave but crashes Matlab 2014. Mathworks won't help because my contract has run out. Any ideas would be helpful.

X = [1 , 2 ,3 , 4 ,5];
Y = [1,4,9,4, 1];
xdata = X(:);
A = [xdata.^2, xdata, ones(size(xdata))]
b = log(Y(:));
x = A\b
mu    = -x(2)/x(1)/2;
sigma = sqrt( -1/2/x(1) );
A0    = exp(x(3)+mu^2/(2*sigma^2));

14 个评论
显示 12更早的评论隐藏 12更早的评论

Walter Roberson 2019-1-2

The number of vendors who will commit to downwards compatibility is vanishingly small.

Committing to downwards compatibility requires that formal proof methods be used to prove software 100% correct in every respect -- which in turn really just shifts the burden to proving that the specification is 100% correct.

You cannot commit to downards compatibility without formal proof methods because otherwise the risk is too high that you might have had a bug in a past release, and if you ever had a bug then backwards compatibility requires that all later releases have exactly the same bug in every respect.

Committing to downwards compatability is not possible for any software that relies on external interfaces provided by an operating system, such as graphics systems, because those could have bugs that you would then need to replicate forever in the name of downward compatibility.

Effectively, committments to downward compatibility can only be made for programs that accept only US-ASCII 65 character input and emit only US-ASCII 65 character output, with no file I/O, and with no dynamic memory allocation (only fixed size static memory.) A program which is sized to run in 650 megabytes of memory at some historical point is not backwards compatible if at some later point it permits using up to 1 gigabyte of memory.

John D'Errico 2019-1-2

Essentially, it means you can't use MATLAB for this, at least a too old release on a too new computer. I'm actually surprised MATLAB even started up. Complain to your institution (as if that will help.) But you can try. Argue that as new students enter the system, they are bringing in new (current) computers.