<?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>MQX Software SolutionsのトピックPost mortem analysis in MQX</title>
    <link>https://community.nxp.com/t5/MQX-Software-Solutions/Post-mortem-analysis-in-MQX/m-p/353004#M11494</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Apologies if this thread already exists somewhere.&amp;nbsp; I'm working on a project and I'm in the process of tightening the screws a bit.&amp;nbsp; I've been looking at the routines in kernel/klog.c, and a few routines to get information related to stack usage.&amp;nbsp; Is there a way to get an actual stack trace?&amp;nbsp; Minimally, I'm interested in being able to get a stack trace (with args) of a failed task at the time of failure and dump it out to persistent storage for later retrieval.&amp;nbsp; Any advice would be *greatly* appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance,&lt;/P&gt;&lt;P&gt;Rob&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 16 Jan 2015 23:26:05 GMT</pubDate>
    <dc:creator>strlen</dc:creator>
    <dc:date>2015-01-16T23:26:05Z</dc:date>
    <item>
      <title>Post mortem analysis in MQX</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/Post-mortem-analysis-in-MQX/m-p/353004#M11494</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Apologies if this thread already exists somewhere.&amp;nbsp; I'm working on a project and I'm in the process of tightening the screws a bit.&amp;nbsp; I've been looking at the routines in kernel/klog.c, and a few routines to get information related to stack usage.&amp;nbsp; Is there a way to get an actual stack trace?&amp;nbsp; Minimally, I'm interested in being able to get a stack trace (with args) of a failed task at the time of failure and dump it out to persistent storage for later retrieval.&amp;nbsp; Any advice would be *greatly* appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance,&lt;/P&gt;&lt;P&gt;Rob&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Jan 2015 23:26:05 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/Post-mortem-analysis-in-MQX/m-p/353004#M11494</guid>
      <dc:creator>strlen</dc:creator>
      <dc:date>2015-01-16T23:26:05Z</dc:date>
    </item>
    <item>
      <title>Re: Post mortem analysis in MQX</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/Post-mortem-analysis-in-MQX/m-p/353005#M11495</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Rob,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please check the attached document and let me know if this helps,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Have a great day,&lt;BR /&gt; Sol &lt;BR /&gt; &lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 19 Jan 2015 22:49:57 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/Post-mortem-analysis-in-MQX/m-p/353005#M11495</guid>
      <dc:creator>soledad</dc:creator>
      <dc:date>2015-01-19T22:49:57Z</dc:date>
    </item>
    <item>
      <title>Re: Post mortem analysis in MQX</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/Post-mortem-analysis-in-MQX/m-p/353006#M11496</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hey Sol,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for getting back to me.&amp;nbsp; Sorry if I'm being a bit dense, but where is the attached document? :smileyhappy:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best,&lt;/P&gt;&lt;P&gt;Rob&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 Jan 2015 05:55:29 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/Post-mortem-analysis-in-MQX/m-p/353006#M11496</guid>
      <dc:creator>strlen</dc:creator>
      <dc:date>2015-01-20T05:55:29Z</dc:date>
    </item>
    <item>
      <title>Re: Post mortem analysis in MQX</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/Post-mortem-analysis-in-MQX/m-p/353007#M11497</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The document is attached to my replay, in addition you can find this doc at the path: C:\Freescale\Freescale_MQX_4_1\doc\tools\cw&amp;nbsp; (MQX_PerfTool_Getting_Started)&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Regards&lt;BR /&gt; Sol &lt;BR /&gt; &lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 Jan 2015 14:25:33 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/Post-mortem-analysis-in-MQX/m-p/353007#M11497</guid>
      <dc:creator>soledad</dc:creator>
      <dc:date>2015-01-20T14:25:33Z</dc:date>
    </item>
    <item>
      <title>Re: Post mortem analysis in MQX</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/Post-mortem-analysis-in-MQX/m-p/353008#M11498</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Unfortunately, I don't think that's going to do it.&amp;nbsp; I'm looking for a way of programatically determining the stack trace without having to use a debugger.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 22 Jan 2015 01:57:57 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/Post-mortem-analysis-in-MQX/m-p/353008#M11498</guid>
      <dc:creator>strlen</dc:creator>
      <dc:date>2015-01-22T01:57:57Z</dc:date>
    </item>
    <item>
      <title>Re: Post mortem analysis in MQX</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/Post-mortem-analysis-in-MQX/m-p/353009#M11499</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please check the below thread and let me know if this helps!!&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.nxp.com/thread/306129"&gt;MQX Tools best way to post mortem dying task?&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Have a great day,&lt;BR /&gt; Sol &lt;BR /&gt; &lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 22 Jan 2015 21:29:54 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/Post-mortem-analysis-in-MQX/m-p/353009#M11499</guid>
      <dc:creator>soledad</dc:creator>
      <dc:date>2015-01-22T21:29:54Z</dc:date>
    </item>
  </channel>
</rss>

