Jump to content

LabVIEW DLL


bjustice

Recommended Posts

Posted

I have a LabVIEW-built DLL.  (2021 SP1, 64-bit, Linux)

I am calling this DLL cyclically by a RUST application over FFI.

Never on the first DLL call, but sometimes on subsequent DLL calls, I am hitting a segfault:

LabVIEW caught fatal signal
21.0.1f6 - Received SIGSEGV
Reason: address not mapped to object
Attempt to reference address: 0x170

I can't seem to figure out why this is happening.  It has something to do with the fact that I am needing to call the DLL several times, with little wait time in-between calls.
I suspect that the DLL is unloading, and then reloading between each call. 
And I suspect that this unloading might be creating a weird race condition with the runtime engine, where the runtime engine is still busy unloading the DLL from the first call, when the 2nd call happens.

Any ideas are welcome.  Scratching my head on this one.

Join the conversation

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

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
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.