Bus Errors?

[Fairlight]

Confusious (Tim Fischer) say:
> Mark,
> 
> I actually ended up rebuilding each index in the file and the issue went
> away.  It doesn't really make any sense.  I could use all of the indexes
> without issue and the code did not call on any index (as you saw).  This
> would also kind of explain why it went away in the past - I probably rebuilt
> the index for some other reason.

How odd.

> What confuses me is that I've gotten this issue in the past, removed 4-5
> lines of *comments* from the top of the prc table, rebuilt the tok table and
> everything was fine.

How even-more-odd.  At that point, it sounds like it could be a memory
corruption error that -leads- to a math error.  I can think of ways it
could happen.  Something gets shifted around and does a math operation it
really was never intended to do, based on incorrect memory locations, and
it can't handle it.  That's a fairly likely scenario, actually.

> Is this a bug in FilePro?

I'm not in a position to say with any authority.  But if you can remove
-comments- from a table and ameliorate the situation, gut instinct says
yes, almost certainly.  I've talked to enough people to know you can
code fP tables to cause segv's without it being a filePro bug.  But just
removing comments?  That's a bit of a different creature, IMHO.

But I could be dead wrong.  I'm not Ken, I can't look at the code.

Have you updated to the latest version, or are you on an older version?

> Thanks for the response though.

Isn't much.  Not much anyone except fP-Tech will be able to help with
though, aside from prodding you to get the latest version if you haven't
already--and if you have, I'd get the sample files and an official report
to fpsupport ASAP.  Wish I could do more for ya.

Bests,

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