RemoteDebuggerConsole: cxa_atexit.c💯 Assertion "1 != NULL" failed

Hi, I am building a custom 32 bit Linux system which runs Xojo apps. With the new 2016r4.1 I do get an error message when trying to start either RemoteDebuggerConsole or Remote Debugger Desktop on my target:

./RemoteDebuggerConsole
RemoteDebuggerConsole: cxa_atexit.c:100: __new_exitfn: Assertion `l != NULL’ failed.
Aborted

./Remote\ Debugger\ Desktop
Remote Debugger Desktop: cxa_atexit.c:100: __new_exitfn: Assertion `l != NULL’ failed.
Aborted

ldd shows that all libraries are there:

LD_TRACE_LOADED_OBJECTS=1 ./RemoteDebuggerConsole
linux-gate.so.1 (0xb775a000)
librt.so.1 => /lib/librt.so.1 (0xb774d000)
libdl.so.2 => /lib/libdl.so.2 (0xb7748000)
libpthread.so.0 => /lib/libpthread.so.0 (0xb772c000)
libc.so.6 => /lib/libc.so.6 (0xb75b0000)
/lib/ld-linux.so.2 (0xb775b000)

I have also copied over all necessary Xojo libraries (otherwise I get a different error).

Could it be something along the lines of: http://stackoverflow.com/questions/27270536/what-is-the-output-of-the-parent-process-atfer-terminating-a-child ?

My custom system is running kernel 4.8.11 with glib 2.24, all built with gcc 6.2.0.

Best Regards

In case anyone else has this issue, it has been silently fixed in 2017r1.1 (possibly also in 2017r1, I did not test that one).

It may be worth noting that only “Remote Debugger Desktop” has been fixed, RemoteDebuggerConsole still has the same issue.

Best Regards