Segfault omq-proxy (proxy.cpp) x86_84 openwrt linux musl

[necro-nemesis]

For whatever reason this occurs on x86_64 and does not occur on aarch64 when running on the Rockchip RK3328.

Package built through cross-compilation on the OpenWRT SDK in the same manner as working targets.
Package installs without compliant.
Daemon runs for a short period, segfault occurs, procd restarts the process when set to unlimited attempts.
As it runs for a short period. Connects to .loki domains. Segfaults then crashes. Procd (OpenWRT's version of systemd) repeats the cycle restarting the process as it should.

Archive includes lokinet and and lokinet-vpn + omq-proxy core dumps x 3

core_dumps.zip

[necro-nemesis]

I have re-compiled binaries with symbols but the lokinet binary is too large for it to be posted here.

[necro-nemesis]

Put any investigation on HOLD based on my further findings.

The issue does not appear if I build the custom OpenWRT image on 21.02 vice using using 22.03 release images where the fault occurs.

Either 22.03 has an issue or their release images are borked. Will report back based on further investigation and findings. I am to going to establish the compatibility with release images and/or 22.03 in light of this discovery.

Will leave this open until the problem is further defined as to weather it's a Lokinet omq fix or it's attributable to OpenWRT.

[necro-nemesis]

Further investigation appears that the segfault is related to OpenWRT 22.03.

I have tested whether it could be related to an issue with release images through building the same images and testing with them. I have also tested between 21.02 and 22.03 on different arch's. The common fault is with using 22.03 and does not present itself when using 21.02 on any of the arch's tested. Currently 21.02 is without issue. I will continue to investigate if others are reporting segfault issues with the newer 22.03 on other previously stable packages.

[necro-nemesis]

From looking for reports and reading through the few I was able to find; Segfaults with 22.03 doesn't appear to be commonly reported which leads me to believe debugging is going to be required to resolve issues with the latest OpenWRT release. 21.02 remains rock solid.