RTC Forums

Hi Danijel,

I compile my app with RTC_DEBUG and I have this errors in myapp.ERROR.log:

2017-08-04 15:25:44.540; TRtcSockSynThread.RunJob Sock.Exec_Message(4) Exception! EAccessViolation: Access violation
2017-08-04 15:26:27.745; TRtcSockSynThread.RunJob Sock.Exec_Message(4) Exception! EAccessViolation: Access violation
2017-08-04 15:27:50.263; TRtcSockSynThread.RunJob Sock.Exec_Message(4) Exception! EAccessViolation: Access violation
2017-08-04 15:28:33.367; TRtcSockSynThread.RunJob Sock.Exec_Message(4) Exception! EAccessViolation: Access violation
2017-08-04 15:33:31.191; TRtcSockSynThread.RunJob Sock.Exec_Message(4) Exception! EAccessViolation: Access violation
etc

Problem should be in somewhere in my code (in RtcFunction.OnExecute, etc) or it's should be bug in RTC SDK ?

p.s. problem happens on CentOS 6, app compiled with Lazarus 1.6.4. I know it's not supported, but I need to know where to find bug - in your code or in my code.

It's an Access Violation, which means that the problem could be anywhere and completely unrelated to the location where the exception is being raised. The only thing I can say, is that the Access Violation is caught by a RTC Worker Thread while executing the TRtcSocketBaseSyn.Exec_StartReading method, where data is being read from a socket and then processed.

In a nutshell, the problem COULD be in your code or something you are calling from within your code, or ... since you are using an unsupported compiler and targeting unsupported platform, the problem could also be wrong type association in the "rtcTypes.pas" unit (for example, 32-bit pointers versus 64-bit) or any other platform-specific code that doesn't exactly match the platform you are targeting (like sockets or zlib, for example).

Best Regards,
Danijel Tkalcec

After some debugging and testing I can report: it's not RTC SDK issue !

It's related to threading problems in FPC RTL and/or my Linux distro.

Ok. Thank you for your feedback.

Best Regards,
Danijel Tkalcec