Jump to content

Common Error and Fix - LabVIEW caught fatal signal


Recommended Posts

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! :)

Link to post
Share on other sites
  • 11 months later...
  • 13 years later...
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).

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.