Debugging optimized code

Make the right tradeoffs to get the easiest possible debugging and fastest possible optimization

From the developerWorks archives

Rajan Bhakta

Date archived: December 20, 2016 | First published: October 15, 2013

Making a program more debuggable and optimizing it requires an inherent tradeoff. The more the source code is optimized, the less it looks like the original code. Consequently, debugging the program is much harder, because the actual code run doesn't correspond well with the original code. This article describes a continuum of tradeoffs that can provide the right balance between debugging a program and making it run fast. This article also describes how to debug inlined functions and procedures.

This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some steps and illustrations may have changed.



static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=Rational
ArticleID=948043
ArticleTitle=Debugging optimized code
publish-date=10152013