https://devzone.nordicsemi.com/f/nordic-q-a/22798/call-stack-window-does-not-display-local-valuesI&#39;m running a debug session. I set a break point inside of function services_init on line 201. I ran the run up to break point command The processor pauses on line 201 as expected. However, the stack window only displays variables local toen-USTelligent Community 13Wed, 14 Jun 2017 21:02:43 GMThttps://devzone.nordicsemi.com/thread/89630?ContentTypeID=1Wed, 14 Jun 2017 21:02:43 GMT137ad170-7792-4731-bb38-c0d22fbe4515:b532cd9c-d7c4-4068-996f-384149ca8166MichaelNordicUser<p>Great thanks, I&#39;m able to step over code now without &quot;jumping&quot;. In one of my projects however, the run command which runs the code to the nearest break point, doesn&#39;t appear to be running. Any idea why? When I click on the run command icon, and it grays out without any apparent effect.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/89629?ContentTypeID=1Wed, 14 Jun 2017 20:22:54 GMT137ad170-7792-4731-bb38-c0d22fbe4515:c2280e2d-3b12-496e-baed-606c1994f305H&#229;kon Alseth<p>Hi,</p> <p>Try going into project settings -&gt; C/C++ tab, and set optimization level to -O0. Then re-compile and flash the firmware again. When enabling higher optimization, the compiler looks for patterns in your all of your code, squishes similar sections together, and the outcome is not as streamlined as your source code. This is the reason why debugging with high optimization may give inconsistent &quot;jumps&quot; in code, and the call stack may not show all variables correctly.</p> <p>Cheers, Håkon</p><div style="clear:both;"></div>