SIGSEGV FATAL error

PLCnext Technology & PLCnext Controls
1

Hi, i’ve got the followed fatal error that’s happen sometimes :

15.07.26 09:08:54.465 Arp.System.Commons.Chrono.Timer                              ERROR - Exception occurs in timer 'Sample:500': vector::_M_range_check: __n (which is 0) >= this->size() (which is 0)
15.07.26 09:08:54.470 Arp.System.Commons.Runtime.SignalHandler                     FATAL - Signal SIGSEGV occured.
Stacktrace:
   at: VectoredHandler_SIGSEGV(int, siginfo_t*, void*)
   at: /lib/libc.so.6(+0x30680) [0xb6630680]

But i don’t use C++ in my programme, so don’t know how it’s possible. Maybe a bug in a PLC next library ?

I use the version 2023.6 of PLCNEXT and a 2023.0.7 firmware.

Can anyone help me to identify/correct this segmentation fault ?

2

looking at this line: ERROR - Exception occurs in timer ‘Sample:500’: vector::_M_range_check: __n (which is 0) >= this->size() (which is 0)

it looks like a variable as 0 as value, but it’s not possible because it looks like to be a vector. So maybe in some of your programs you have some calculi giving the value 0 that is not accepted

3

Hello

Please contact fr_support_automation@phoenixcontact.fr. The sigsegV error was present in older FW (> 2026.0 LTS). The best solution is to update the PLC and PlcNext to the actual versions. Please notice that any change from FW<2026 to FW > 2026 will request a complete update of the application. Must read before firmware update