diff options
| author | Vadim Yanitskiy <axilirator@gmail.com> | 2018-08-14 18:57:53 +0700 |
|---|---|---|
| committer | Vadim Yanitskiy <axilirator@gmail.com> | 2018-08-14 19:17:43 +0700 |
| commit | 381370b82ae1f2dd3b62770b72b028c576f7b9c3 (patch) | |
| tree | 1e9f0dd532ee198787ffa1429c752d888b0b099a | |
| parent | d8d4d8caaef686ddb77cee05ed1299ba9e9f5dfb (diff) | |
osmo-msc: track the use of talloc NULL memory contexts
Tracking NULL memory contexts allows one to detect memory chunks,
allocated outside the application's root context, which in most
cases are results of some mistake.
In b874486e8e48f033204bfcc86871dd851266d440 the repotring of
NULL-context state was introduced, but without asking talloc
to track the use of NULL memory contexts it doesn't make sense.
Change-Id: I4b5e3946ee21c7d0ed6c66b1059dbce5ad312f88
| -rw-r--r-- | src/osmo-msc/msc_main.c | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/src/osmo-msc/msc_main.c b/src/osmo-msc/msc_main.c index 2159d656a..1a10278b0 100644 --- a/src/osmo-msc/msc_main.c +++ b/src/osmo-msc/msc_main.c @@ -521,6 +521,9 @@ int main(int argc, char **argv) { int rc; + /* Track the use of talloc NULL memory contexts */ + talloc_enable_null_tracking(); + msc_vty_info.copyright = osmomsc_copyright; tall_msc_ctx = talloc_named_const(NULL, 1, "osmo_msc"); |