Common Error and Fix - LabVIEW caught fatal signal

[Jim Kring]

Many people who are attempting to run LabVIEW on Linux will come accross this error when running LabVIEW:

segmentation fault: LabVIEW caught fatal signal 7.0 - Received SIGSEGV.

Reason: address not mapped to object

The quick fix is described in an NI Knowledge Base entry here.

Worked for me!

[pallen]

Thanks Jim!!

I just put together a new desktop, and this was the first time I'd seen this error. The fix worked perfectly.

:worship:

[Suquen]

Hi Jim Kring,

Would you post the solution here? cos, the link seems expired!!!

Thanks.

[dadreamer]

1 hour ago, Suquen said:

cos, the link seems expired!!!

That article is available on Web Archive.

[Rolf Kalbermatter]

On 9/21/2020 at 1:11 PM, Suquen said:

Hi Jim Kring,

Would you post the solution here? cos, the link seems expired!!!

Thanks.

Are you using LabVIEW 7.1????? If you use a newer version this should not fix any problem as this specific problem was actually fixed in LabVIEW 7.1.1. The problem was that the LabVIEW enumeration of directory entries assumed that the first two returned entries were the . and .. entries. Since LabVIEW 7.1.1 the Linux version doesn't have that assumption (the Windows version still had at least until recently and that can cause different problems when accessing a Samba mounted directory).