title: Analyze .exe/.dll (Windows PE) files for code bloats
body: <p>Let's say I have a project with a dozen of different modules which produce one resultant DLL, how can I analyze it so that I can identify the actual file size that each module/functions contribute? I know it might be impossible with a Release build where much information has been stripped, but how about if I have the full source and can do a Debug build?</p>
  
  <p>Also, if there are big static variables defined somewhere, is there a way I can easily locate them?</p>
  
  <p><em>Bonus question</em>: How about Linux ELF files?</p>