Project

General

Profile

Actions

Feature #3913

closed

allow applications to override libsmpp34 memory allocation

Added by laforge about 5 years ago. Updated almost 5 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
-
Start date:
04/09/2019
Due date:
% Done:

100%

Spec Reference:

Description

As we have seen in #3910 / #3912, we've had smpp related memory leaks for ages, as we assume all our heap allocations are seen in the talloc report. This isn't true for libsmpp34 which calls malloc() and free() directly.

Let's introduce a mechanism by which libsmpp34-using applications can override the memory allocator functions.


Related issues

Related to OsmoMSC - Bug #3912: memory leak in SMPP interfaceResolvedlaforge04/09/2019

Actions
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)