Seg Violation on Linux

[Fairlight]

At Mon, Nov 07, 2005 at 08:55:43PM -0500 or thereabouts, 
suspect Nancy Palmquist was observed uttering:
> 
> I have been messing with it and any other setting for the tok flags 
> seems to make it worse.  I looked at the long variables and deleted a 
> few that were not used and it seems to squeak by with no error.
[snip]
> I have messed with this so long I am sure it is a memory related issue. 
>   Changing variable sizes, seems to affect the location of the crash point.

Funny you should mention that...   

You say it sometimes happens and sometimes doesn't.  There are two things
that might cause that:  data-massaged bugs, or a problem with the physical
memory.

Is it ECC RAM?  If not, have they the resources to replace the RAM in the
machine and see if it goes away?

Lest you think I'm joking, a lot of sporadic segv's tend to happen on
systems with bad RAM.  I've seen it happen myself on multiple systems over
the last 12-13 years.

Mightn't even -be- your code--or fP.  Just a thought...

mark->