On Thu, Dec 13, 2012 at 09:03:09PM +0100, Thomas Weber wrote:
> On Thu, Dec 13, 2012 at 09:33:22PM +1100, Drew Parsons wrote:
> > I then tried octave-dbg (3.6.3-2), again with libhdf5-openmpi-7. It
> > still crashes. But as before, awkwardly it does not crash when run
> > inside gdb, so I still ca
On Thu, Dec 13, 2012 at 09:33:22PM +1100, Drew Parsons wrote:
> I then tried octave-dbg (3.6.3-2), again with libhdf5-openmpi-7. It
> still crashes. But as before, awkwardly it does not crash when run
> inside gdb, so I still can't collect a backtrace.
How about running it under strace?
And you
On 13 December 2012 05:33, Drew Parsons wrote:
> On Wed, 2012-12-12 at 22:49 +0100, Thomas Weber wrote:
>>
>> Please install octave-dbg and try again (not that I think it will help,
>> but maybe we are lucky just once and get more information).
>>
>
> I then tried octave-dbg (3.6.3-2), again with
On Tue, 2012-12-11 at 20:38 -0500, Mike Miller wrote:
>
> Or is it any hdf5 variant? Have you tried installing the non-openmpi
> libhdf5-7 with the original octave packages to see if that also
> crashes on you? I didn't see whether you had tried that yet.
>
I've now tried octave (3.6.3-2, the ne
On 12 December 2012 16:49, Thomas Weber wrote:
> On Mon, Dec 10, 2012 at 01:03:05PM +1100, Drew Parsons wrote:
>> Is the octave-core file useful?
> The default answer to that question is "no". In fact, I cannot remember
> a single case where the octave-core file was of use.
It's been renamed to
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 Tue, Dec 11, 2012 at 7:55 PM, Drew Parsons wrote:
>
> I've got the full build log now. It just confirms that hdf5 was not
> found and therefore not built against:
>
> checking hdf5.h usability... no
> checking hdf5.h presence... no
> checking for hdf5.h... no
> configure: WARNING: HDF5 library
On Mon, 2012-12-10 at 18:41 -0500, Mike Miller wrote:
>
> Can you verify that your locally built package, the one that does not
> panic, did indeed link in libhdf5-openmpi-7? E.g.:
I've got the full build log now. It just confirms that hdf5 was not
found and therefore not built against:
checkin
On Mon, 2012-12-10 at 18:41 -0500, Mike Miller wrote:
> On Mon, Dec 10, 2012 at 5:55 AM, Drew Parsons wrote:
> > I presume this libhdf5 dependency is the cause of the bug, which means
> > you should be able to reproduce it by replacing libhdf5-7 with
> > libhdf5-openmpi-7.
>
> Not here, I am unabl
On Mon, Dec 10, 2012 at 5:55 AM, Drew Parsons wrote:
> I presume this libhdf5 dependency is the cause of the bug, which means
> you should be able to reproduce it by replacing libhdf5-7 with
> libhdf5-openmpi-7.
Not here, I am unable to reproduce on amd64 with libhdf5-openmpi-7
installed and libhd
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 -
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 -- stopping myself...
attempting to save variables to `octave-core'...
save to `octave-core' complete
Se
16 matches
Mail list logo
