: bug

[Ben Abbott]

On May 25, 2008, at 2:40 PM, yakup murat mert wrote:
> Ben Abbott <bpabbott at mac.com> wrote:
> On May 25, 2008, at 2:24 PM, yakup murat mert wrote:
> > Ben Abbott wrote:
> > On May 24, 2008, at 8:32 PM, yakup murat mert wrote:
> >
> > > clear all
> > >
> > > instruction closes everytihing including octave ....
> > >
> > > yakup murat mert
> >
> > I encountered such a problem earlier in the month.
> >
> > http://www.nabble.com/crash-on-%22clear-all%22-after-call-to-%22mesh%22-tt17049780.html
> >
> > In addition to David & Bill's questions; What preceded the "clear  
> all"
> > and what is displayed to the console afterward?
> >
> > Ben
> >
> > I am using Windows and downloaded it from SourceForge.net. Version
> > of installed material is from octave-3.0.1-vs2008-setup.exe file.
> >
> > Normally when i type "clear all" on octave , all windows collapse
> > including console... It does not give an error because it has no
> > time to give an error. Everything gets closed...
> >
> > However when i use "qtoctave" A popup window says "octave crashed
> > and it will be restarted " And console gives the following...
> >
> > panic: Segmentation violation -- stopping myself...
> > attempting to save variables to `octave-core'...
> > save to `octave-core' complete
> >
> > Then restarts....
>
> Ok. This does not appear to be related to the problem I encountered.
>
> I suggest you give more detail regarding David and Bill's questions.
>
> What version of Windows are you using, and what service pack?
> Hopefully someone with a similar installation can verify the problem
> (I don't have a windows box).
>
> Does a crash result if "clear all" is the first command?
>
> Ben
>
> I am using windows XP SP2.... I used "clear all" instruction  at  
> beginning of the script.

I'm still hoping one of Octave's windows based developers will chime  
in. In the meantime, does the same result occur when you type "clear  
all" as the initial command, or does it only occur when in a script?

Also, is there any chance your octaverc file predates 3.0.1? ...  
perhaps there is something in that script that eventually produces the  
seg-fault, and if so, we might find that is can be reproduced on other  
OS's.

Ben