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 Kenneth Brody
Sent: Wednesday, December 05, 2007 12:34 PM
To: Scott Nelson
Cc: filepro-list at lists.celestial.com
Subject: Re: Segmentation violation

 
Quoting Scott Nelson (Wed, 05 Dec 2007 09:09:16 -0800):

> Look at the size of the processing table, both in number of lines and
> bytes.  I have found that long tables on large processing tables can
> cause this due to a memory boundry overlap.  Try removing old unused
> code, or comments and shorten the table.
[...]

Do you have any samples you can send to fpsupport which demonstrate this?

-- 
KenBrody at BestWeb dot net        spamtrap: <g8ymh8uf001 at sneakemail.com>
http://www.hvcomputer.com
http://www.fileProPlus.com
_______________________________________________
Filepro-list mailing list
Filepro-list at lists.celestial.com
http://mailman.celestial.com/mailman/listinfo/filepro-list

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?