Actions
Bug #3611
closedSegfault setting logging level all, when omitting 'logging enable'
Start date:
10/01/2018
Due date:
% Done:
100%
Spec Reference:
Description
~$ telnet 127.0.0.1 4237 Trying 127.0.0.1... Connected to 127.0.0.1. [welcome text here] OsmoTRX> enable OsmoTRX# loggi OsmoTRX# logging le OsmoTRX# logging level a OsmoTRX# logging level all debug OsmoTRX# logging level all debug Connection closed by foreign host.
Reading symbols from /osmo-gsm-tester-trx/last_run/osmo-trx/bin/osmo-trx-uhd...done. [New LWP 13282] [New LWP 13312] [New LWP 13310] [New LWP 13313] [New LWP 13311] [New LWP 13314] [New LWP 13306] [New LWP 13305] [New LWP 13307] [New LWP 13308] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/osmo-gsm-tester-trx/last_run/osmo-trx/bin/osmo-trx-uhd -C /osmo-gsm-tester-trx'. Program terminated with signal SIGSEGV, Segmentation fault. #0 log_set_log_level (target=target@entry=0x0, log_level=1) at logging.c:740 740 logging.c: No such file or directory. [Current thread is 1 (Thread 0x7fd2905f1740 (LWP 13282))] (gdb) bt #0 log_set_log_level (target=target@entry=0x0, log_level=1) at logging.c:740 #1 0x00007fd28f569517 in logging_level_force_all (self=<optimized out>, vty=<optimized out>, argc=<optimized out>, argv=0x7ffcc7ed1550) at logging_vty.c:394 #2 0x00007fd28f5614c1 in cmd_execute_command_real (vline=vline@entry=0x56229c1ae420, vty=vty@entry=0x56229c634cb0, cmd=0x0) at command.c:2293 #3 0x00007fd28f563db1 in cmd_execute_command (vline=vline@entry=0x56229c1ae420, vty=vty@entry=0x56229c634cb0, cmd=cmd@entry=0x0, vtysh=vtysh@entry=0) at command.c:2326 #4 0x00007fd28f565f90 in vty_command (buf=<optimized out>, vty=0x56229c634cb0) at vty.c:420 #5 vty_execute (vty=0x56229c634cb0) at vty.c:684 #6 vty_read (vty=<optimized out>) at vty.c:1426 #7 0x00007fd28f568051 in client_data (fd=0x56229c1ae2f8, what=1) at telnet_interface.c:135 #8 0x00007fd28f33b5de in osmo_fd_disp_fds (_eset=0x7ffcc7ed2180, _wset=0x7ffcc7ed2100, _rset=0x7ffcc7ed2080) at select.c:217 #9 osmo_select_main (polling=<optimized out>) at select.c:257 #10 0x000056229b55ca47 in main (argc=<optimized out>, argv=<optimized out>) at osmo-trx.cpp:592
On the other hand, "set-all" and "force-all" seems to work fine.
This is most probably related to last logging patches, it used to work fine before.
Updated by fixeria over 5 years ago
- Project changed from OsmoTRX to libosmocore
- Category set to libosmocore
Just confirmed with OsmoBTS and OsmocomBB. So it's a global problem.
Updated by fixeria over 5 years ago
It's interesting that this problem doesn't appear in VTY configuration:
OsmoBTS> en OsmoBTS# configure terminal OsmoBTS(config)# log stderr OsmoBTS(config-log)# logging level all debug OsmoBTS(config-log)# logging level all everything
but if you enable logging to the VTY:
OsmoBTS# logging level all FOO
it will crash.
Updated by neels over 5 years ago
I notice that the error only occurs when omitting 'logging enable'.
libosmocore/tests/logging/logging_vty_test.vty should be modified to test for this.
Updated by neels over 5 years ago
- Subject changed from osmo-trx-uhd: Segfault setting logging level all to Segfault setting logging level all, when omitting 'logging enable'
- Status changed from New to In Progress
- % Done changed from 0 to 90
Updated by neels over 5 years ago
- Status changed from In Progress to Resolved
- % Done changed from 90 to 100
Actions