Bug in mbed_alloc_wrappers.cpp

[DBS06]

Description

regarding issue #11960

Setting
"platform.heap-stats-enabled": false,
"platform.memory-tracing-enabled": false,
in mbed_app.json does not deactivate tracing in mbed_alloc_wrappers.cpp

Summary of change

Documentation

---

Pull request type

[x] Patch update (Bug fix / Target update / Docs update / Test update / Refactor)
[] Feature update (New feature / Functionality change / New API)
[] Major update (Breaking change E.g. Return code change / API behaviour change)

---

Test results

[] No Tests required for this change (E.g docs only update)
[x] Covered by existing mbed-os tests (Greentea or Unittest)
[] Tests / results supplied as part of this PR

---

Reviewers

---

Release Notes

Summary of changes

Impact of changes

Migration actions required

[0xc0170]

Can you add more to Description - what is this fixing , etc - details from the issue report.

[ciarmcom]

@DBS06, thank you for your changes.
@ARMmbed/mbed-os-core @ARMmbed/mbed-os-maintainers please review.

[evedon]

This change is not required, see #11960 (comment)

[DBS06]

@evedon should I close this PR?

[bulislaw]

This should work for both cases when the macro is not defined and where it set to false, why do we want to close it? Sure it doesn't address the whole configuration, but it does the right thing for this module. Or am I missing something?

[0xc0170]

I would expect it to work, as it is in this PR

[kjbracey]

I do approve this, but I would approve it harder it if also adjusted the JSON to change the default nulls to false.

EDIT: Although, on second thoughts, that might actually be a small breakage risk. It's possible some application or external code might be doing #ifdef itself and hence relying on null == off. Maybe do that separately, and file for 6.0. This is fine as a patch.

[mbed-ci]

Test run: SUCCESS

Summary: 11 of 11 test jobs passed
Build number : 1
Build artifacts