-
Notifications
You must be signed in to change notification settings - Fork 3k
Update mbed_mem_tracing config option #8487
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
platform/mbed_lib.json
Outdated
"error-filename-capture-enabled": { | ||
"help": "Enables capture of filename and line number as part of error context capture, this works only for debug and develop builds. On release builds, filename capture is always disabled", | ||
"value": false | ||
}, | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This spacing fix should be a separate commit
As you learned the lesson about #ifdef vs #if and config options, is this documented anywhere ? |
@0xc0170 Good point, we do have some tickets for improving the config systems docs for 5.11 that we're working on. |
d5d5358
to
0f661fb
Compare
So if we're revering a breaking change, does that make this a breaking change? |
@cmonr This is not a full revert of the last change. The breaking change from before was having a macro defined would cause a warning. If someone is using the old PR (say 5.10.2) and they updated to this they should see no issue as they'd have already moved to using the config system. If a user is still using the old macro define (<5.9) this will work as expected too. |
0f661fb
to
d8782c0
Compare
Fixed the merge conflict. @0xc0170 are the whitespace changes alright now? |
Removing breaking change, as this is not. |
I still see them as part of the commit that does other changes, can you create a new one? |
Ahhh shoot rebase put the spaces back in...one second |
33465f8
to
7ecb974
Compare
Move the memory tracing enabled macro to a config option but revert the !defined -> #if changes to no longer cause breaking changes.
7ecb974
to
a2ac895
Compare
@0xc0170 Updated |
I requested also core team to review (meanwhile we run CI) /morph build |
Build : FAILUREBuild number : 3490 |
The errors looks unrelated (one example does not fit, another failure is in the example python script) /morph build |
Build : FAILUREBuild number : 3493 |
Found in the build_wrapper job:
/morph build |
@kegilbert This should probably be fixed:
Also found in the build_wapper job |
Build : SUCCESSBuild number : 3495 Triggering tests/morph test |
Exporter Build : SUCCESSBuild number : 3112 |
Test : SUCCESSBuild number : 3279 |
For the occasional historian or lurker, it turns out that #8487 (comment) was allowed into master because the Travis CI version of doxygen is woefully out of date (Dec 2013 was when it was released). |
Description
This reverts most of commit 9b53d12
#8106 taught me that I can use a default value of null to have the config macro be not defined in mbed_config.h. Reverting my old changes that moved all of the mbed_mem_tracing option checks from
#if !defined(....)
to#if ...
which caused minor breaking changes.Move the memory tracing enabled macro to a config option but revert the !defined -> #if changes to no longer cause breaking changes as #7402 did.
Pull request type