BUG: BSD - No PFAUTOKSIZE SET - SEGV

[John Esak]

There is a bug in BSD that produces a SEGV when filePro should be putting up
an error about toksize.

Do the following:

Put PFTOKSIZE=100000 and PFFORMTOKSIZE=100000 into the config file (omit
PFAUTOKSIZE).

Define a one field file. 1 character, no edit type.
Accept the default Screen 0
Build an automatic table that looks like this, only 6 lines, 6 variables:

  1  -------   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -
       . If:
.
       Then: aa(128,,g)
.
  2  -------   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -
       . If:
.
       Then: ab(128,,g)
.
  3  -------   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -
       . If:
.
       Then: ac(128,,g)
.
  4  -------   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -
       . If:
.
       Then: ad(128,,g)
.
  5  -------   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -
       . If:
.
       Then: ae(128,,g)
.
  6  -------   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -
       . If:
.
       Then: af(128,,g)
.


Then, enter the file with dclerk as in:

  dclerk stand -s0

Try and Add a record... or go to an existing record (should you have a file
like this one built already). The SEGV happens. To remedy, just put
PFAUTOKSIZE=100000 or some other smaller number in the config file and all
becomes well.

I think this condition should cause filePro to complain about not enough
tokzie, not SEGV. Actually, it would be great if filePro could complain
about the _kind_ of toksize that was inadequate as well, like:  tokenization
size too small, increase PFAUTOKSIZE.

cc'd to support at fptech.com

John Esak
Visit The FP Room www.tinyurlcom/97y9u 24/7

The filePro Survivor Series
Complete Video Training for filePro itself. www.valar.com/training