Cellular Network Infrastructure » Radio Access Network » OsmoBSC

For some reason, BSC_Tests.ttcn fails on all tests with "ERROR" since 2018-03-13, see e.g. https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-bsc-test/109/

I've tracked the problem down to some C++ crash with backtrace in the generated C++ decoder for CtrlMessage upon receiving the CTRL response "GET_REPLY 290783505 bts.0.oml-connection-state degraded" from OsmoBSC.

The smallest test case to reproduce it is:

testcase TC_ctrldec() runs on test_CT {
       var charstring inp := "GET_REPLY 290783505 bts.0.oml-connection-state degraded";

       var CtrlMessage cmsg := dec_CtrlMessage(inp);
       log(cmsg);
}

What's odd is that I cannot find any changes to the CTRL ttcn3 code in our repository (nor the IPA_Emulation.ttcnpp underneath), nor the libosmoctrl code during that timeframe at all.

The same code builds fine on TITAN 6.3.1 on Debian unstable.

In the past we've already had to work-around TITAN 6.1.0 bugs for things that were working perfectly fine in later releases like 6.2.0, 6.3.0 or 6.3.1. Upstream TITAN also has made it very clear that they strongly recommend running the latest release and they won't support anything else.