Has PlotXY gone buggy in CVI 7.0? Sporadic crashes with Stack overflow in debug mode.

[blakney]

I am having trouble porting code written in earlier version of CVI (probably 4.0 or 5.0)and that has ported fine through CVI 6 but now periodically crashes (>10% of the time ) in version 7. This function is used extensively when zooming into plotted spectra.

The error in debug mode always stops at PlotXY with a non fatal Stack Overflow error. I have checked the data I am sending to the graph and the datacount and depth of the x and y arrays all match.

This code is unmodfied from the version functioning on version 6. I was wondering if there is someone familiar with the changes to the PlotXY algorithm that might produce such crashes.

[LuisG]

There was a bug in CVI 7 that could be causing this behavior. To find out for sure, edit your graph control and disable autoscaling for the *top* x-axis. (even if you're not using the top x-axis). Then see if you can still reproduce the problem.

Luis
NI

[blakney]

I checked and true to form the autoscaling on the top X axis was on (and not being used). Simply truning off the autoscaling appears to have fixed the problem in preliminary tests.

Thanks.

[pauliatucd]

This is a very good advice, it helped me with my problems getting stack overflow. I hope there will be a fix of this bug soon. Many thanks.

[duncan carter]

There seems to be a similar bug in PlotWaveform.
int PlotWaveform (int panelHandle, int controlID, void *yArray, int numberOfPoints, int yDataType, double yGain, double yOffset, double initialX, double xIncrement, int plotStyle, int pointStyle, int lineStyle, int pointFrequency, int color);

Some combinations of numberOfPoints and xIncrement cause the dll that I'm working on to crash. I wasted several hours on this problem before I remembered seeing this thread previously.

[LuisG]

Duncan,

I'm sorry that this cost you a lot of time.

The bug that I was referring to in this thread could cause the stack overflow to happen with any plotting function, so if you noticed the problem and then it went away when you disabled autoscaling in the top x-axis, then it's definitely the same bug.

Luis

[duncan carter]

Thanks, Luis. You are quick. ;-))