On Mon, Dec 10, 2012 at 01:03:05PM +1100, Drew Parsons wrote:
> The interaction with gdb is odd. An error is found, but the octave
> command line appears regardless. I think octave catches the error,
> but doesn't panic inside gdb. So no backtrace is available. The gdb
> behaviour is:
> $ gdb oct
On Mon, 2012-12-10 at 06:05 +0100, Rafael Laboissiere wrote:
>
> I cannot reproduce this bug on my amd64 testing system. We need more
> information on your problem.
I've got a positive result from a local rebuild.
The clean rebuild using pbuilder gave the same segfault.
A local build however
On Mon, 2012-12-10 at 08:45 +0100, Sébastien Villemot wrote:
>
> A few more questions:
>
> - what is your currently selected BLAS implementation? (display it with
> update-alternatives --display libblas.so.3). If it is
> not /usr/lib/libblas/libblas.so.3, please try again with that one
> selected
Control: severity -1 important
[downgrading the severity because seems to affect only the reporter, so
does not make the package useless for most people]
Hi,
Le lundi 10 décembre 2012 à 13:03 +1100, Drew Parsons a écrit :
> Package: octave
> Version: 3.6.2-5
> Severity: grave
> Justification: re
On Mon, 2012-12-10 at 06:05 +0100, Rafael Laboissiere wrote:
>
> I cannot reproduce this bug on my amd64 testing system. We need more
> information on your problem. As a first step, could you please check
> Bug#695434?
In regards to Bug#695434, I do have java problems at the moment, the bug
i
package octave
tags 695551 unreproducible moreinfo
stop
* Drew Parsons [2012-12-10 13:03]:
Package: octave
Version: 3.6.2-5
Severity: grave
Justification: renders package unusable
octave has just started failing to start, with the error message:
$ octave -q
panic: Segmentation fault -
6 matches
Mail list logo
