Actions
Bug #3713
closedosmo-bsc abort()s in ttcn3-bsc-sccplite TC_ho_int testcase
Start date:
11/27/2018
Due date:
% Done:
100%
Spec Reference:
Description
I can not reproduce this if TC_ho_int is the first test I run. Running the whole suite with docker does cause this issue so it seems some lingering state triggers this.
The core file shows the following:
(gdb) bt full #0 __GI_abort () at abort.c:125 act = {__sigaction_handler = {sa_handler = 0x0, sa_sigaction = 0x0}, sa_mask = {__val = {18446744073709551615 <repeats 16 times>}}, sa_flags = 0, sa_restorer = 0x0} sigs = {__val = {32, 0 <repeats 15 times>}} #1 0x00007f8033abd020 in osmo_panic () from /usr/lib/x86_64-linux-gnu/libosmocore.so.11 No symbol table info available. #2 0x0000000000432dca in conn_get_bts (conn=<optimized out>) at ../../include/osmocom/bsc/gsm_data.h:1242 No locals. #3 ho_or_as (vty=0xf0d2d0, argv=0xf0dcb0, argc=6) at bsc_vty.c:1668 conn = 0xf0dcb0 new_bts = 0x7fff8a84a590 bts_nr = 0 trx_nr = 0 ss_nr = 856498279 bts_nr_new = 514 action = 0x6 <error: Cannot access memory at address 0x6> #4 0x00007f80343567c5 in ?? () from /usr/lib/x86_64-linux-gnu/libosmovty.so.4 No symbol table info available. #5 0x00007f803435b429 in vty_read () from /usr/lib/x86_64-linux-gnu/libosmovty.so.4 No symbol table info available. #6 0x00007f803435d4d9 in ?? () from /usr/lib/x86_64-linux-gnu/libosmovty.so.4 No symbol table info available. #7 0x00007f8033ab38f0 in osmo_select_main () from /usr/lib/x86_64-linux-gnu/libosmocore.so.11 No symbol table info available.
The code in ho_or_as iterates through the subscr_conns and just assumes there is an lchan present for all of them. I guess this is no longer the case and we should prepend a conn->lchan && to the if statement?
Files
Actions