<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>LPCXpresso IDEのトピックLXPXpresso debugging</title>
    <link>https://community.nxp.com/t5/LPCXpresso-IDE/LXPXpresso-debugging/m-p/592327#M29946</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by Martin_ on Thu Aug 25 07:32:46 MST 2011&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;Hello,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I've have a problem debugging with LPCXpresso (V4.0.6, embedded Artists&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;LPC11C24 evalBoard and embedded Artists&amp;nbsp; LPC1114 evalBoard, different&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;computers).&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;The attached project file contain one test_function, which never called, and a&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;main function with a for loop. When I debug this project on an evalBoard, the&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;debugger jumps after some single steps in main-function into the non-called&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;function and later back to main.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;If I trunc the test_function to several lines the debugger behaves as aspected.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Has the debugger limitations in function-length or file-length?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 15 Jun 2016 21:29:04 GMT</pubDate>
    <dc:creator>lpcware</dc:creator>
    <dc:date>2016-06-15T21:29:04Z</dc:date>
    <item>
      <title>LXPXpresso debugging</title>
      <link>https://community.nxp.com/t5/LPCXpresso-IDE/LXPXpresso-debugging/m-p/592327#M29946</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by Martin_ on Thu Aug 25 07:32:46 MST 2011&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;Hello,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I've have a problem debugging with LPCXpresso (V4.0.6, embedded Artists&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;LPC11C24 evalBoard and embedded Artists&amp;nbsp; LPC1114 evalBoard, different&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;computers).&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;The attached project file contain one test_function, which never called, and a&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;main function with a for loop. When I debug this project on an evalBoard, the&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;debugger jumps after some single steps in main-function into the non-called&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;function and later back to main.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;If I trunc the test_function to several lines the debugger behaves as aspected.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Has the debugger limitations in function-length or file-length?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 21:29:04 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPCXpresso-IDE/LXPXpresso-debugging/m-p/592327#M29946</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T21:29:04Z</dc:date>
    </item>
    <item>
      <title>Re: LXPXpresso debugging</title>
      <link>https://community.nxp.com/t5/LPCXpresso-IDE/LXPXpresso-debugging/m-p/592328#M29947</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by CodeRedSupport on Thu Aug 25 08:18:03 MST 2011&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;This is caused by a (fairly rare) bug in the linker/debugger when unused code is eliminated. As you function is never called, the linker removes it from the executable. If you remove the "--gc-sections" option from the Linker/miscellaneous options, this will prevent the linker from removing unused code and you won't see this odd behavior.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 21:29:05 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPCXpresso-IDE/LXPXpresso-debugging/m-p/592328#M29947</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T21:29:05Z</dc:date>
    </item>
    <item>
      <title>Re: LXPXpresso debugging</title>
      <link>https://community.nxp.com/t5/LPCXpresso-IDE/LXPXpresso-debugging/m-p/592329#M29948</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by Martin_ on Thu Aug 25 10:21:20 MST 2011&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks a lot for your answer. I tried it and the scary behavior doesn't occur. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;lt;close&amp;gt;&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 21:29:05 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPCXpresso-IDE/LXPXpresso-debugging/m-p/592329#M29948</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T21:29:05Z</dc:date>
    </item>
  </channel>
</rss>

