Thu 21 Aug 2014 05:26:14 PM UTC, original submission:
This is an issue I was seeing on 32-bit version 3.8.1 on my old beater computer but I am also seeing it on 64-bit 3.8.2 on my new computer.
I am seeing a lot of crashes after using CTRL-C to interrupt a running program. Not every time but if I start and stop enough times (less than 10) then it will exit rudely with no message. This is with octave-cli, not related to the GUI.
I recompiled without optimizations and with debugging symbols + gdb, as described here: http://wiki.octave.org/Debugging_Octave
However it seems CTRL-C doesn't really interrupt octave in the gdb environment, rather it passes control to the gdb prompt. So it wasn't possible to replicate the bug and get a decent bug report.
The following script produces the problem, if you start and stop it (e.g. at the octave prompt type weird_bug2 then after a few seconds press CTRL-C, then repeat). On my system it will segfault after 2-10 tries.
%-----------------------------------------------
function weird_bug2()
data = randn(1000,1000,4)+i*randn(1000,1000,4);
X = randn(7,7,4)+i*randn(7,7,4);
for j = 1:100
im = convn(data,X,'same');
imagesc(dot(im,im,3))
title(num2str(j))
drawnow
end
%------------------------------------------------
The only other clue I have is that is only happens with complex variables (data, X).
|