title: How much footprint does C++ exception handling add
body: <p>This issue is important especially for embedded development. Exception handling adds some footprint to generated binary output. On the other hand, without exceptions the errors need to be handled some other way, which requires additional code, which eventually also increases binary size.</p>
  
  <p>I'm interested in your experiences, especially:</p>
  
  <ol>
  <li>What is average footprint added by your compiler for the exception handling (if you have such measurements)?</li>
  <li>Is the exception handling really more expensive (many say that), in terms of binary output size, than other error handling strategies?</li>
  <li>What error handling strategy would you suggest for embedded development?</li>
  </ol>
  
  <p>Please take my questions only as guidance. Any input is welcome.</p>
  
  <p>Addendum:  Does any one have a concrete method/script/tool that, for a specific C++ object/executable, will show the percentage of the loaded memory footprint that is occupied by compiler-generated code and data structures dedicated to exception handling?</p>