MAP file analysis - where's my code size comes from?
问题 I am looking for a tool to simplify analysing a linker map file for a large C++ project (VC6). During maintenance, the binaries grow steadily and I want to figure out where it comes from. I suspect some overzealeous template expansion in a library shared between different DLL's, but jsut browsign the map file doesn't give good clues. Any suggestions? 回答1: This is a wonderful compiler generated map file analysis/explorer/viewer tool. Check if you can explore gcc generated map file. amap : A