Actions
Feature #3913
closedallow applications to override libsmpp34 memory allocation
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
Updated by laforge about 5 years ago
- Related to Bug #3912: memory leak in SMPP interface added
Updated by laforge about 5 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 100
Patch in https://gerrit.osmocom.org/#/c/libsmpp34/+/13561
We need to make sure to do the talloc integration in osmo-msc, once this is merged.
Updated by laforge about 5 years ago
- % Done changed from 100 to 90
https://gerrit.osmocom.org/#/c/osmo-msc/+/13562 implements the actual talloc integration in osmo-msc
Updated by laforge almost 5 years ago
- Status changed from In Progress to Resolved
- % Done changed from 90 to 100
both patches merged months ago
Actions
