Segmentation violation

[Scott Walker]

-----Original Message-----
From:
filepro-list-bounces+scottwalker=ramsystemscorp.com at lists.celestial.com
[mailto:filepro-list-bounces+scottwalker=ramsystemscorp.com at lists.celest
ial.com] On Behalf Of Kenneth Brody
Sent: Thursday, December 06, 2007 10:05 AM
To: filepro-list at lists.celestial.com
Subject: RE: Segmentation violation

Quoting George (Thu, 6 Dec 2007 01:31:36 -0500):
[...]
>
> 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.

Prior to 5.6, there was a limit of 128K on the compiled code size.
Starting with 5.6, this has been increased to 2MB of compiled code.

Note that, to the best of my knowledge, exceeding this limit would
give a "tok table too small" error.  I don't recall any reports that
it would appear to compile and then fail at runtime with an "invalid
opcode" error.

Note, too, that this is compiled _code_ size, not the size of the tok
file, which includes definitions of fields, lookups, arrays, and so
on, as well as symbol tables and other information.

-- 
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


Ken,

How do we tell what the compiled _code_ size is?

I have a large prc table of 4795 lines.

When I record it and check the syntax it says:

	Token Table Size:  198400

When I say to create Runtime Table it created a tok file that is 616779
bytes long.

Where do I determine if I am approaching the compiled _code_ size
limitation of fp 5.0?

Regards,

Scott Walker
RAM Systems Corp.
ScottWalker at RAMSystemsCorp.com
Ph: (704) 896-6549
Fx: (704) 896-7458