<?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のトピックRe: Invisible breakpoints</title>
    <link>https://community.nxp.com/t5/LPCXpresso-IDE/Invisible-breakpoints/m-p/549980#M11222</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 Tue Dec 13 02:02:50 MST 2011&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;Which MCU are you debugging? In particular note that Cortex-M0 based MCUs only have 4 hardware breakpoints.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;From the very limited information you have provided, it is hard to say exactly what else might be causing you problem. But one thing to watch is that breakpoints are stored in the workspace, and by default are effectively project independent. Thus if you set a breakpoint in one file, and have a file of the same name in another project within the workspace, then if you debug the second project you may hit breakpoints unexpectedly (or have all your breakpoint units consumed unexpectedly).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;You can configure your debug launch configuration such that breakpoints are set with absolute filenames to avoid this issue though.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;To do these, right click on the project and select&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Launch Configurations -&amp;gt; Open Launch Configurations -&amp;gt; Debugger&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Then select the "Main" tab and tick the "Use full file path to set breakpoints" option.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Note - this assumes you have already debugged the project in question. If not simply select the "Create Launch Configurations" option first.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;CodeRedSupport&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 16 Jun 2016 00:37:24 GMT</pubDate>
    <dc:creator>lpcware</dc:creator>
    <dc:date>2016-06-16T00:37:24Z</dc:date>
    <item>
      <title>Invisible breakpoints</title>
      <link>https://community.nxp.com/t5/LPCXpresso-IDE/Invisible-breakpoints/m-p/549979#M11221</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by Sharadanand on Mon Dec 12 05:42:18 MST 2011&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;I am using LPCXpresso IDE, while debugging debugger stops at certain lines when there is no break points and I can not add more break points:(&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 Jun 2016 00:37:23 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPCXpresso-IDE/Invisible-breakpoints/m-p/549979#M11221</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-16T00:37:23Z</dc:date>
    </item>
    <item>
      <title>Re: Invisible breakpoints</title>
      <link>https://community.nxp.com/t5/LPCXpresso-IDE/Invisible-breakpoints/m-p/549980#M11222</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 Tue Dec 13 02:02:50 MST 2011&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;Which MCU are you debugging? In particular note that Cortex-M0 based MCUs only have 4 hardware breakpoints.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;From the very limited information you have provided, it is hard to say exactly what else might be causing you problem. But one thing to watch is that breakpoints are stored in the workspace, and by default are effectively project independent. Thus if you set a breakpoint in one file, and have a file of the same name in another project within the workspace, then if you debug the second project you may hit breakpoints unexpectedly (or have all your breakpoint units consumed unexpectedly).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;You can configure your debug launch configuration such that breakpoints are set with absolute filenames to avoid this issue though.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;To do these, right click on the project and select&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Launch Configurations -&amp;gt; Open Launch Configurations -&amp;gt; Debugger&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Then select the "Main" tab and tick the "Use full file path to set breakpoints" option.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Note - this assumes you have already debugged the project in question. If not simply select the "Create Launch Configurations" option first.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;CodeRedSupport&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 Jun 2016 00:37:24 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPCXpresso-IDE/Invisible-breakpoints/m-p/549980#M11222</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-16T00:37:24Z</dc:date>
    </item>
    <item>
      <title>Re: Invisible breakpoints</title>
      <link>https://community.nxp.com/t5/LPCXpresso-IDE/Invisible-breakpoints/m-p/549981#M11223</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by Sharadanand on Thu Dec 15 05:43:25 MST 2011&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;The info was useful I shall follow your instructions and I shall do debugging.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I am using LPC1114&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 Jun 2016 00:37:24 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPCXpresso-IDE/Invisible-breakpoints/m-p/549981#M11223</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-16T00:37:24Z</dc:date>
    </item>
  </channel>
</rss>

