Segmentation violation

[George]

-----Original Message-----
From: filepro-list-bounces+flowersoft=compuserve.com at lists.celestial.com
[mailto:filepro-list-bounces+flowersoft=compuserve.com at lists.celestial.com]
On Behalf Of Fairlight
Sent: Wednesday, December 05, 2007 10:38 PM
To: filepro-list at lists.celestial.com
Subject: Re: Segmentation violation

 
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

I don't know what you are talking about, but this is a known limit in
filePro processing tables prior to 5.6.  May have also been fixed (or
enhanced) in 5.0.15.
The invalid op code was the error filePro was reporting when the table
exceeded the limit.