[Pkg-octave-devel] Bug#695434: Bug#695434: octave: Seg fault in __contourc__

[Mike Miller]

On Sat, Dec 8, 2012 at 10:59 AM, Rafael Laboissiere wrote:
> * Pierre.St-Laurent at uqar.ca <Pierre.St-Laurent at uqar.ca> [2012-12-08 14:06]:
>>
>>
>> Ok, I saved the array in a .mat file and attached it to this email. I can
>> trigger the code every time by starting a fresh octave session and typing:
>>
>> load array.mat; % Provides array z of size 469x760 ii = 1:size (z,2); %
>> From contourc.m jj = 1:size (z,1); % From contourc.m c = __contourc__ (ii,
>> jj, z, [500 500]); % will seg fault %c = __contourc__ (ii, jj, z, [1000
>> 1000]); % will work fine
>>
>> The last line shows that the behavior depends on the actual contour level
>> requested. 500 cause seg fault, but 1000 is fine. The same instruction works
>> all the time on my other laptop that has squeeze.
>
>
> Thank you for the data and the code.  I can confirm the bug on amd64, but it
> does not happen on i386.  This is probably an upstream bug, but may also be
> related to something architecture-dependent we do for building the package.
> @Sébastien: could you take a look at this, please?

I confirm on amd64, but only with the octave-java package installed
and loaded. If I run octave with --norc it does not segfault. If I
apt-get remove octave-java, it no longer crashes. Can you both try
again without octave-java installed?

-- 
mike