[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Testing MinGW Octave-3.4.2 binaries
From: |
Tatsuro MATSUOKA |
Subject: |
Re: Testing MinGW Octave-3.4.2 binaries |
Date: |
Wed, 13 Jul 2011 09:35:58 +0900 (JST) |
Hello
I have confirmed 'clear all' caused crash when windows package is installed.
octave:6> pkg list
Package Name | Version | Installation directory
--------------+---------+-----------------------
odepkg *| 0.6.10 | ...\OctaveBuild\share\octave\packages\odepkg-0.6.10
windows *| 1.0.8 | ...\OctaveBuild\share\octave\packages\windows-1.0.8
octave:7> clear all
panic: Segmentation violation -- stopping myself...
attempting to save variables to `octave-core'...
save to `octave-core' complete
I have used development source and built and execute octave on windows 7 64 bit
HomePremium.
The error seem to be version and environment independent bug.
Regards
Tatsuro
--- On Wed, 2011/7/13, Tatsuro MATSUOKA wrote:
> Hello
>
> Excuse me that I did not understand the situation correctly
> I will to install windows package to octave-3.4.2 and test it.
>
> As far as I remember, loading windows package causes 'clear all' error on the
> octave-3.2.4 provided by Benjamin.
>
> The error seems to happen also on the octave-3.4.2 on MinGW.
> I hope this error will be eliminated by your efforts and I will cooperate
> with you as possible.
>
> Regards
>
> Tatsuro
> --- On Wed, 2011/7/13, Philip Nienhuis wrote:
>
> > Tatsuro MATSUOKA wrote:
> > > Hello
> > >
> > > On my environment, windows 7 64 bit HomePremium,
> > > The 'clear all' command seems not induce crash.
> > >
> > > octave:1> clear all
> > > octave:2>
> >
> > To provoke the crash you need to have the windows package installed &
> > loaded.
> > So it is not a (core) Octave issue. That is, does the "Octave should not
> > crash" principle apply to (compiled) packages too (i.e., .oct files)?
> > Should Octave be immune to them as well?
> >
> > Anyway I'm curious if the "clear all" crash also happens on Win7 (with the
> > windows package loaded).
> >
> > Philip
> >
>