Bug #4300
closedosmo-bsc segfaults when logging is enabled
100%
Description
to reproduce:
run osmo-bsc in terminal (to see the segfault)
telnet localhost 4242
enable
logging enable
logging filter all 1
logging level force-all debug
close connection via <ctrl-d>
usr/bin/osmo-bsc -c /etc/osmocom/osmo-bsc.cfg -s logging level cc (debug|info|notice|error|fatal) logging level mgcp (debug|info|notice|error|fatal) % dyn_ts_allow_tch_f is deprecated, rather use msc/codec-list to pick codecs <0013> ../../../git/src/vty/telnet_interface.c:104 Available via telnet 127.0.0.1 4242 <0015> ../../git/src/input/ipaccess.c:859 enabling ipaccess BSC mode on 0.0.0.0 with OML 3002 and RSL 3003 TCP ports <001a> ../../../git/src/ctrl/control_if.c:911 CTRL at 127.0.0.1 4249 <0023> ../../../git/src/libosmo-mgcp-client/mgcp_client.c:777 MGCP client: using endpoint domain '@mgw' <0007> ../../../git/src/osmo-bsc/osmo_bsc_sigtran.c:494 Initializing SCCP connection to MSC msc-0 ... BTS 0 reported connected PCU version 0.7.0 BTS 0 reported connected PCU version 0.7.0 BTS 0 reported connected PCU version 0.7.0 Segmentation fault (core dumped)
the same happens when 'set-all' is used (not only with 'force-all'
Updated by laforge over 4 years ago
- Assignee set to pespin
- Priority changed from Normal to High
can you please always make sure to include the exact version of the program used when making bug reports? Otherwise it's guesswork to try to reproduce it.
Updated by laforge over 4 years ago
just did a very quick attempt with master of a few days ago, couldn't reproduce.
> ./osmo-bsc --version OsmoBSC version 1.4.0-dirty
Updated by neels over 4 years ago
already fixed by this? http://git.osmocom.org/libosmocore/commit/?id=f8fe48e7fb2f0fef722bcd0d4cf37f6697ae86b4
Updated by roh over 4 years ago
- Assignee deleted (
pespin) - Priority changed from High to Normal
OsmoBSC version 1.5.0
on a sysmobts2100 image 201705-testing from november this year
Updated by roh over 4 years ago
- Assignee set to pespin
- Priority changed from Normal to High
Updated by pespin over 4 years ago
- Status changed from New to Feedback
- Assignee changed from pespin to roh
Can you try running following binary in the sysmobts and see if you can still reproduce the issue?
https://jenkins.osmocom.org/jenkins/view/osmo-gsm-tester/job/osmo-gsm-tester_build-osmo-bsc/lastSuccessfulBuild/artifact/osmo-bsc.build-7737.tgz
It contains all required deps, so simply uncompress it and set LD_LIBRARY_PATH to $untared_dir/lib.
Updated by pespin over 4 years ago
Ah nevermind, that one is not built for ARM like we do for osmo-bts-sysmo ;)
Updated by pespin over 4 years ago
You can use the libosmocore from here however (Current master), this way we may be lucky and don't see the crash, which means it's fixed in master (probably neel's link):
https://jenkins.osmocom.org/jenkins/view/osmo-gsm-tester/job/osmo-gsm-tester_build-osmo-bts-sysmo/3608/artifact/osmo-bts-sysmo.build-3608.tgz
Updated by roh about 4 years ago
- Status changed from Feedback to Resolved
- % Done changed from 0 to 100
tried to reproduce again with
OsmoBSC version 1.6.0.4-2fa97
-> seems fixed. cannot reproduce anymore
