AnsweredAssumed Answered

Segmentation Violation

Question asked by VRFuser on Feb 22, 1998
        I have run into something similar with Memory Segmantation errors. 
     I finally managed to isolate them down to the DECALRD GLOBALS objects.
      Out project uses globals to keep track of various states and we were
     trying to use DECLARED VARIABLES to keep globals in scope within
     libraries.  This seemed to lead to segmentation errors, and when the
     DECLARATIONS were removed, the problems went away.  I wish I had time
     to pursue this problem, but we have a work-around now know
     how it goes sometimes.
        I don't know if this applies to your problem, but thought I would
     share it anyway.  Good Luck.
     Thomas Groleau
     Tucson, Arizona

______________________________ Reply Separator _________________________________
Subject: Segmentation Violation
Author:  "Allen K. Lair" <> at CCGATE
Date:    1/16/98 9:42 AM

I have recently upgraded from VEE 3.21 to 4.01, and when my program does a
showpanel() on a function, I get "Segmentation Violation (Signal=11), etc. etc.,
Error Number: 979".  I have tried removing the showpanel() function and
replacing it using 4.01, as well as changing the properties of the user function
to Show Panel on Execute, both with the same result.  Does anyone have a
Any help would be appreciated,
Allen K. Lair
Senior Technologist
Communications Research Centre
Kanata, Ontario, Canada
Phone: (613) 998-2374
       (613) 991-9034
Fax:   (613) 991-9035