Project

General

Profile

Actions
Copy link

Bug #3007

closed

make sure all libosmocore code can tolerate FSMs without event names

Added by laforge about 6 years ago. Updated about 6 years ago.

Status:
Resolved
Priority:
Urgent
Assignee:
stsp
Category:
-
Target version:
-
Start date:
02/26/2018
Due date:
% Done:

0%

Spec Reference:

Description

See #2924, apparently it cannot deal with this situation gracefully

Related issues

Related to OsmoMSC - Bug #2924: osmo-msc MGCP FSM has no event namesResolveddexter02/10/2018

Actions
Related to libosmocore - Bug #3008: print big fat error message in case somebody registers osmo_fsm without event namesResolvedstsp02/26/2018

Actions
Actions
Copy link
 #1

Updated by laforge about 6 years ago

  • Related to Bug #2924: osmo-msc MGCP FSM has no event names added
Actions
Copy link
 #2

Updated by laforge about 6 years ago

  • Related to Bug #3008: print big fat error message in case somebody registers osmo_fsm without event names added
Actions
Copy link
 #3

Updated by stsp about 6 years ago

  • Status changed from New to In Progress

Proposed a patch in https://gerrit.osmocom.org/#/c/6950/

As far as I can see, this is the only place in libosmocore which dereferences this pointer without checking for NULL.

Actions
Copy link
 #4

Updated by stsp about 6 years ago

  • Status changed from In Progress to Resolved

Above change has been merged.

Actions
Copy link

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)