eliotstock gravatar image

Posted 2014-12-02 13:59:44 +0100

blogs->all

Visualising your memory usage

The linker in the GCC toolchain, ld, produces a *.Map file which shows you how the memory on your micro is being used. This file is a goldmine of information but it's a bit difficult for humans to absorb.

I've whipped up a web page which uses the excellent D3.js library to draw a visualisation of your memory usage, using the *.Map file as input. Blocks of memory are drawn proportionally so it's easy to see how much memory you have left and where it's all being used. Click on a block to zoom in on it.

You can run the tool right off the github project page, or download it and modify it for your needs. Pull requests welcome.

https://github.com/eliotstock/memory

image description

Cheers,

Eliot

4 comments

MrQuincle gravatar image

Posted Dec. 2, 2014, 5:30 p.m.

Nice! Did you use specific flags to get more information? I only see FLASH and RAM and very little used out of both. See this prog.map file.

eliotstock gravatar image

Posted Dec. 2, 2014, 5:56 p.m.

Because you have very long symbol names, like this...

.text.ZN4func6detail16function_manager19templated_call_copyIPFvbESaIS4_EEEvRNS0_20manager_storage_typeERKS6

... ld is wrapping the memory details onto the next line which is breaking the tool.

MrQuincle gravatar image

Posted Dec. 3, 2014, 2:30 p.m.

Ah, you are right. If I join the lines together with .text in them:

ex -c '%g/\.text/j' -c "wq" prog.map

then I get a lot more info. A better one would be the one that leaves alone the lines that are already on one line:

ex -c '%g/\.text\S*[\s]*$/j' -c "wq" prog.map

And succeeded by replacing .text.blah with .text:

sed -i 's/\.text\S*/.text/g' prog.map

The only thing left is that the items get really small when you're program gets big. I've to look in the zooming options in your code, but thanks again!

eliotstock gravatar image

Posted Dec. 3, 2014, 5:48 p.m.

Thanks for the pull request! Merged.

Sign in to comment.