Segmentation violation

[Jay R. Ashworth]

On Wed, Dec 05, 2007 at 11:50:37AM -0500, Jaime Perry wrote:
> What causes are there for segmentation violations?  A client of ours 
> just sent an email with screen prints of about 10 different segmentation 
> errors all of which occurred  while navigating  their menus.   The 
> errors are happening on random  menus and with different key strokes.  
> Most of the errors are generated when they hit "X" to exit a menu but 
> some happen when hitting other keys to enter a menu option.  They are 
> using Filepro 5.0.07D4 on a SCO Unix box (version 5.0.7).

*Lots* of things can cause fP to dump core, including syntax errors in
termcap entries, malformed processing lines because you were working in
vi and got your colon count screwed up... in general; filePro isn't big
on looking for dirty data in things it believes are internal, but which
aren't always.  (By which I mean, things that it normally reads having
written them itself and expecting them not to be externally modified).

But in your case, where untouched code suddenly starts puking, Mark's
right: run memtest86+ overnight.  Check for horribly dusty hardware as
well, and you might also be losing a power supply.

Cheers,
-- jra
-- 
Jay R. Ashworth                   Baylink                      jra at baylink.com
Designer                     The Things I Think                       RFC 2100
Ashworth & Associates     http://baylink.pitas.com                     '87 e24
St Petersburg FL USA      http://photo.imageinc.us             +1 727 647 1274

	     Witty slogan redacted until AMPTP stop screwing WGA