Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Enhance memap, and configure depth level #4392
Generates a detailed report by analysing static memory information from the map file.
The information from the map file is combined with the information from the BUILD directory (compiled objects and path to these objects), including the main application and user libraries.
In addition, it's now possible to visualise compiler libraries and identify other miscellaneous objects introduced by the toolchain.
By default, memap generates a report with depth=2, but it's possible to specify a different depth level, and even to enable a full report (depth=0).
It has been tested with the three major toolchains: GCC, ARM and IAR compiler.
Looking good. A few questions:
Sure, the depth number can be passed to memap - see here:
I'd need a bit of help to be able to pass a parameter from
I agree. Commit coming soon.
@MarceloSalazar Thanks for the PR.
Also, we recommend PRs follow Chris Beam’s seven rules of great commit messages. This helps us with the release notes.
To match this format, please change the subject line to the imperative mood by changing it to "Enhance memap, and configure depth level"
Thanks so much for your help.
These changes look very good. I have some style comments and naming bikeshedding comments below.
This was referenced
May 31, 2017
@miklis noticed that the jenkins/pr-head Details link actually pointed to the wrong Jenkins job - the one for #4887. Restarting the build from the correct job seems to have fixed the issue so the update should come to the right place.
Creating two PRs from the same branch probably confused Jenkins/github a bit.