FW: fatal error: unexpected SIGSEGV in emulator mode

[Jose Lerebours]

On 12/2/21 8:51 AM, Fairlight via Filepro-list wrote:
> This did not read like a hardware issue to me.  Not unless the RAM was
> dying.  My first thought was memory corruption, based on the error
> message.  SEGVs are almost always memory related.  The most common cause
> is a bad pointer, or code which results in an invalid pointer when
> presented with certain data.  If it's anything to do with hardware, the
> RAM should be the first suspect.  That said, if the rest of the system
> is working, it seems isolated.  I'd try it again after a reboot, when
> all the memory addresses have reset and shifted a bit, and see if it
> persists.  If it does, then I'd look at checking the filesystem, as that
> could affect data and cause this sort of issue.  If that was clean, or
> the problem persists past the point it is repaired, then I'd look at the
> RAM.

I agree 110% here ... things that came to mind were

1. HD sector
2. memory
3. larger than supported file sizes
4. a corrupt filePro map/key segment

Wouldn't `fsck` help to at least verify HD condition in such event?

> I honestly think you're being pretty militant about wanting to toss out
> the baby with the bathwater.  It sounds like an isolated problem which
> may be fixable without upgrading everything under the sun.
lol - not really, I just never understood why people depend on software
to run their business and yet never do anything to keep said software
up to date.

Look, I like classic cars as much as any guy/gal, but I would not take a
1970s car across country if I have never changed the timing belt or even
a change of oil, spark plugs ...  It runs, but will I take it on a cross 
country ride?

Lets wait and see what fpTech has to say about this knowing that they
monitor this list - to a degree ...


-- 
Jose Lerebours
954-559-7186
https://www.asisuites.com
Accounting - Retail - Wholesale - Distribution
Manufacturing - Warehousing - Transportation - eCommerce - Web Development