Project

General

Profile

Actions

Bug #2747

closed

OsmoBSC segfaults on Rx MSC UDT BSSMAP RESET

Added by neels over 6 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Immediate
Assignee:
Category:
-
Target version:
-
Start date:
12/13/2017
Due date:
% Done:

100%

Spec Reference:

Description

cleanly rebuilt OsmoBSC master at 61b0c30cca80cba5522b172b884b2904b91eb516 / I3c278c57880a173df3c4648c9724339d23ce94fd is unable to survive a BSSMAP RESET procedure.

20171213184026287 DMSC <000a> ../../../../src/osmo-bsc/src/osmo-bsc/osmo_bsc_bssap.c:650 Rx MSC UDT BSSMAP RESET
20171213184026287 DMSC <000a> ../../../../src/osmo-bsc/src/osmo-bsc/osmo_bsc_bssap.c:215 RESET from MSC: RI=SSN_PC,PC=0.23.1,SSN=BSSAP,GTI=NO_GT

Program received signal SIGSEGV, Segmentation fault.
0x000055555557b9ff in paging_flush_bts (bts=bts@entry=0x555555986960, msc=msc@entry=0x555555998510) at ../../../../src/osmo-bsc/src/libbsc/paging.c:476
476        llist_for_each_entry_safe(req, req2, &bts->paging.pending_requests, entry) {

backtrace follows

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)