* Sébastien Villemot [2013-01-03 20:14]:
Le jeudi 03 janvier 2013 à 15:17 +0100, Rafael Laboissiere a écrit :
Since it is now stated that this is a real problem, which may cause data
loss to the users, we might raise the severity level and propose a new
patched version for wheezy, based on:
Le jeudi 03 janvier 2013 à 15:17 +0100, Rafael Laboissiere a écrit :
> Since it is now stated that this is a real problem, which may cause data
> loss to the users, we might raise the severity level and propose a new
> patched version for wheezy, based on:
>
> http://hg.savannah.gnu.org/hgweb/o
Control: reassign -1 octave 3.6.2-5
Control: tags -1 + fixed-upstream
* pierre.st-laur...@uqar.ca [2013-01-03 13:27]:
Just in case you haven't seen this, it looks like the bug has been (very recently) fixed upstream:
http://savannah.gnu.org/bugs/?37891
Also, it turned out the bug was in oc
Dear maintainer,
Just in case you haven't seen this, it looks like the bug has been (very
recently) fixed upstream:
http://savannah.gnu.org/bugs/?37891
Also, it turned out the bug was in octave-core, not in octave-java.
Thanks,
Pierre
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists
reassign 695434 octave-java 1.2.8-6
stop
* Mike Miller [2012-12-09 12:45]:
We should leave this open until we have a real fix, or reassign to
octave-java in the BTS, [...]
Done hereby.
Thanks,
Rafael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject o
> I apt-get removed octave-java, and the problem disappeared.
> This is a weird fix but I'm very very happy that it works!
I wouldn't call it a fix, but good information to investigate how to
address this.
We should leave this open until we have a real fix, or reassign to
octave-java in the BTS,
> 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?
I apt-get removed octave-java, and the problem disa
* Mike Miller [2012-12-08 11:20]:
On Sat, Dec 8, 2012 at 10:59 AM, Rafael Laboissiere wrote:
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 w
On Sat, Dec 8, 2012 at 10:59 AM, Rafael Laboissiere wrote:
> * pierre.st-laur...@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; % Prov
* pierre.st-laur...@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 =
* Pierre St-Laurent [2012-12-07 22:14]:
I get a segmentation fault from __contourc__ when using the function
contour() on a certain array. More precisely, the seg fault occur
inside contourc.m at the line:
## Now call __contourc__ for the real work...
c = __contourc__ (ii, jj, z, vv);
Th
Package: octave
Version: 3.6.2-5
Severity: normal
Dear Maintainer,
I'm testing wheezy on a new machine.
I get a segmentation fault from __contourc__ when using the function contour()
on a certain array.
More precisely, the seg fault occur inside contourc.m at the line:
## Now call __contourc__ f
12 matches
Mail list logo
