General Error Handler - crashes

[Sagme_Mi]

Hi,

I am migrating an old PharLabs SW to the new Linux and stumbling over a "general Error handler" issue and I am wondering if I am the only one?!

As the code is pretty old and grown over years there are a lot of general error handlers used to ignore, generate or get the error text.

All of them are set to "no dialog".

When I start the vi via my windows project it immediately crashes in the deploy process.

Small example:

simple test

Error Log on the PXI says its a "SIGSEGV"-Error:

####
#Date: Mon, Mar 25, 2024 11:44:03 AM
#Desc: LabVIEW caught fatal signal
23.1.1f4 - Received SIGSEGV
Reason: address not mapped to object
Attempt to reference address: (nil)
#RCS: unspecified
#OSName: Linux
#OSVers: 6.1.38-rt12
#OSBuild: 393510
#AppName: lvrt
#Version: 23.1.1f4
#AppKind: AppLib
#AppModDate: 
0x00007F7B9E4077DE - <unknown> + 0
0x00007F7B9E4079C8 - <unknown> + 0
0x00007F7B9E40AE92 - <unknown> + 0
0x00007F7B9E40B246 - <unknown> + 0
0x00007F7B9DE63C02 - <unknown> + 0
0x00007F7B9E8412AD - WSendEvent + 18D
0x00007F7B9E842774 - <unknown> + 0
0x00007F7B9E78038D - <unknown> + 0
0x00007F7B9E77AE58 - <unknown> + 0
0x00007F7B9DD4F2CA - <unknown> + 0
0x00007F7B9DD4F4E4 - <unknown> + 0
0x0000000000400DEB - <unknown> + 0
0x00007F7B9F61F57B - <unknown> + 0
0x00007F7B9F61F630 - __libc_start_main + 80
0x0000000000400E91 - <unknown> + 0

On the first look I could not find any Info about this issue?

I mean, its somehow clear the popup wont work, but a crash? without any deeper information why?

And also it worked in PharLabs...

Thanks in advance 🙂

BR

Michael

[Sagme_Mi]

really no one encountered this?

Or someone saw any article about this?

I mean replacing the vi pretty much solves the issue... but still... it annoys me!

PS: we are running the software on PXIs

2023 version of LV/RT/Drivers...