<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Comparing big array in Segger embedded studio in release mode cause the issue</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/45080/comparing-big-array-in-segger-embedded-studio-in-release-mode-cause-the-issue</link><description>I see two different issue from Segger ES. The below piece of code work well in debug mode, comparison of array at 2k and it fails at release mode. Wondering what&amp;#39;s happening? //2kb static uint8_t m_buffer_tx[2048];
static uint8_t m_buffer_rx[2048];
 </description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 20 Mar 2019 14:11:54 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/45080/comparing-big-array-in-segger-embedded-studio-in-release-mode-cause-the-issue" /><item><title>RE: Comparing big array in Segger embedded studio in release mode cause the issue</title><link>https://devzone.nordicsemi.com/thread/177374?ContentTypeID=1</link><pubDate>Wed, 20 Mar 2019 14:11:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:36e96849-4843-41be-bc23-f9faa6afd6df</guid><dc:creator>awneil</dc:creator><description>&lt;p&gt;Are you sure that the logs are enabled in your RELEASE build ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Comparing big array in Segger embedded studio in release mode cause the issue</title><link>https://devzone.nordicsemi.com/thread/177367?ContentTypeID=1</link><pubDate>Wed, 20 Mar 2019 13:59:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4e9eea6c-e164-49e9-860c-ea3e736ee040</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;You can inspect the array while you debug the application in SES:&lt;/p&gt;
&lt;p&gt;1. right click on the array and select Add &amp;lt;variable name&amp;gt; to watch. The &amp;quot;Watch&amp;quot; view should pop up on right side after this.&lt;/p&gt;
&lt;p&gt;2. Right click on the watched variable and select how many elements you want to view (2048)&lt;/p&gt;
&lt;p&gt;&lt;img src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/support-attachments/beef5d1b77644c448dabff31668f3a47-c59dc5b96d674e8691d71ceb0c5a7510/pastedimage1553090070269v1.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;Are you doing anything to these arrays apart from initializing&amp;nbsp;them?&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Comparing big array in Segger embedded studio in release mode cause the issue</title><link>https://devzone.nordicsemi.com/thread/177355?ContentTypeID=1</link><pubDate>Wed, 20 Mar 2019 13:44:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:817a0104-afdc-458d-88ba-7498bb0112a4</guid><dc:creator>iqcosmicxx</dc:creator><description>&lt;p&gt;I try to print the buffer using NRF_LOG_HXDUMP_INFO() for 2048 but the logs are dropped. I compared the 512 bytes they are identical. I guess its something with the Segger ES release doing some aggressive optimization. Thanks for your answer.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Comparing big array in Segger embedded studio in release mode cause the issue</title><link>https://devzone.nordicsemi.com/thread/177152?ContentTypeID=1</link><pubDate>Tue, 19 Mar 2019 16:57:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a3d16e73-84a2-4a6f-9430-f92dab6f0ec2</guid><dc:creator>awneil</dc:creator><description>&lt;p&gt;So look at the differences between your release mode, and debug mode.&lt;/p&gt;
&lt;p&gt;What &lt;strong&gt;debugging&lt;/strong&gt; have you done?&lt;/p&gt;
&lt;p&gt;Have you checked that the buffers are actually consistent?&lt;/p&gt;
&lt;p&gt;ie, how do you know that the problem is in the comparison, and not in the buffer contents?&lt;/p&gt;
&lt;p&gt;Do you have some asynchronous task(s) writing to these buffers ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>