segmentation violation in fp

[Fairlight]

In the relative spacial/temporal region of
Wed, Aug 18, 2004 at 03:19:16PM -0500, Ryan Powers achieved the spontaneous
generation of the following:
> On Wed, Aug 18, 2004 at 03:37:58PM -0400, Fairlight said:
> 
> > I shouldn't worry about the -way- it crashes, so much as the fact that it
> > crashes at all.  Both result in a segv--it's a matter of how cleanly they
> > exit.  Eliminate the crash entirely and how it crashes won't matter.  :)
> 
> At first blush it appears to be identical to a previous bug with
> automatic and input processing tables which could be triggered if the
> files had zero length. The obvious work-around is to delete the file
> and create a new one with something in it, such as a comment.

Makes sense, as Jeremy told me that he ended up with a zero length file.  I
didn't check my file sizes--I just verified the crashing bit.

> This will be fixed in 5.0.14.

Cool.  Thanks for the update!

mark->
-- 
Bring the web-enabling power of OneGate to -your- filePro applications today!

Try the live filePro-based, OneGate-enabled demo at the following URL:
               http://www2.onnik.com/~fairlite/flfssindex.html