I have slightly modified the function as,
% convert3DtoAVI(File, Array)
function  = convert3DtoAVI(filename, Wavefront)
% -- Open file and stuff frames
%OurPath = "c:\\Users\\Owner\\Documents\\Octave\\";
%AVIName = strcat(RootName, SubName);
%filename = strcat(OurPath, AVIName);
printf("convert3DtoAVI: %s\n", filename);
[xSize, ySize, nImages] = size(Wavefront);
Image = Wavefront(:,:,1);
ZeroImage = zeros(size(Image));
% -- This is the avi loop
avi = avifile(filename);
for i = 1:nImages
Image = Wavefront(:,:,i);
% sImage = ScaleImage01(Image);
% addframe(avi, sImage);
and carried out the test
I could reproduce the crash three times. it happened not always but with a probability.
I am using win XP pro sp3.
One of the octave-core dump is
4F 63 74 61 76 65 2D 31 2D 4C 00 08 00 00 00 2E Octave-1-L......
6E 61 72 67 69 6E 2E 00 00 00 00 00 FF 06 00 00 nargin..........
00 73 63 61 6C 61 72 07 00 00 00 00 00 00 08 40 .scalar........@
However, I cannot reproduce error at some moments. ????
Perhaps something is wrong but .....
Sorry I can say any further at this moments.
--- Tatsuro MATSUOKA wrote:
> >I believe Tatsuro has been doing Windows releases, but I'm not certain.
> Benjamin Lindner is the maintainer of the current windows binaries.
> I'm a one of the guys to working with
the octave for windows.
> But I am not directly concerning to the official release of the windows binaries.
> Seeing the SVN repository,with which one can build octave by oneself (tough work), there found
> ffmpeg-0.5 seem to be used.
> The above I can tell at the moment.
> --- Jordi Guti将アrrez Hermoso wrote:
> > 2010/8/1 Kenneth Johnson
> > > THe OS is windows 7.
> > For some reason, I didn't really assimilate the possiblity that you
> > were using Windows. I'm afraid I
know almost nothing about Windows. I
> > believe Tatsuro has been doing Windows releases, but I'm not certain.
> > I imagine the Windows version must ship some sort of version of ffmpeg
> > if the video package works, so the problem is most likely an
> > unfortunate interplay between the Octave code and the ffmpeg code.
> > > A second symptom [...]
> > It is folly to try to diagnose nasal demons without at least a stack
> > trace. I will thus refrain from doing so until hard data is available.
> > > I've got to think about becoming a developer again.............
> > It may well be the fastest way to solve this problem. I may end up
> > solving different problems if I attempt to do so in my cozy Debian
> > environment.
> > _______________________________________________
Help-octave mailing list
> > address@hidden
> > https://www-old.cae.wisc.edu/mailman/listinfo/help-octave
> Are you OK? Online Safety Special Site - Yahoo! JAPAN
> Help-octave mailing list
Are you OK? Online Safety Special Site - Yahoo! JAPANhttp://pr.mail.yahoo.co.jp/security/