Do you analyze the map file in software development, especially when using the GCC compiler? If yes, what are the important aspects you examine in the map file?
Do you analyze the map file in software development, especially when using the GCC compiler? If yes, what are the important aspects you examine in the map file?
No. The map file contains information that is not relevant to most software development.
There are cases where it is useful, like when you are developing for an embedded system. But if you are doing app development on a general-purpose computer like a server, laptop, or desktop, then there is generally no reason to use the map file.
Sorry for not mentioned Embedded software development. How do you analyze MAP file for embedded software development
It's just a text file of all the symbols / addresses / sizes that make up your complete program.
What do you want to know?
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
When you are developing embedded software what are the important aspects you examine in the mapOriginally Posted by Salem
As a general rule, I don't.
If gdb or some other target debugger can make contact with the target device, that is far more preferable as you can just use symbol names.
Where it does become more useful is where all you have is a hex dump of memory and you're trying to figure out what each address represents.
This is laborious and error prone, it's not something you do unless you have no choice.
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
