Segmentation violation

[Scott Nelson]

Fairlight wrote:
> Four score and seven years--eh, screw that!
> At about Wed, Dec 05, 2007 at 10:15:55PM -0500,
> George blabbed on about:
>   
>> Although not in Unix, do you remember back in February of this year when I
>> was getting 
>> Invalid Op Code 254 in tok table. Line 4874, offset 1" errors?
>> I wrote to you:
>> "I think the problem starts to manifest itself after a table tok size
>> reaches or exceeds 262,144 bytes or maybe a little less."
>> We solved the problem by reducing the size of the processing table by moving
>> some code to "called" tables.
>> There is a size limit to the prc and/or tok tables in the pre-5.6 Windows
>> versions.  Maybe the same condition causes a segmentation violation in Unix?
>>     
>
> PRC tables have a limit of 9999 lines, and 127 characters per if or then
> segment, plus the label.
>
> Common sense and observation says that any byte in line 4874 falls well
> within that threshhold.
>
> Further, while fP is notorious for mis-reporting errors, there is no way
> I'd correlate "Invalid Op Code" as even remotely having anything to do with
> the size of a table.
>
> It is amazing the bizzare straws people grasp at when things don't work.
>
> mark->
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list
>
>   

No straws here.  That is the evidence on several systems.  When 
commented lines and code removed, table was shorter and smaller, and the 
opcode and seg vio disappeared.   This is not the first time this has 
happened.  According to Ray, the current .15 does not have this problem.

And this was on SCO OpenServer 5.07 with filePro 5.0.13.

I will send samples to fptech as soon as I can.

Scott