<?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>Other NXP ProductsのトピックS32DS debug call stack</title>
    <link>https://community.nxp.com/t5/Other-NXP-Products/S32DS-debug-call-stack/m-p/2248765#M30699</link>
    <description>&lt;P&gt;&lt;SPAN&gt;在S32DS IDE的调试界面中，从右上角的&lt;/SPAN&gt;&lt;SPAN&gt;Debug&lt;/SPAN&gt;&lt;SPAN&gt;窗口，可以查看到当前程序运行的调用栈(&lt;/SPAN&gt;&lt;SPAN&gt;Call Stack&lt;/SPAN&gt;&lt;SPAN&gt;)；&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;这个调用栈是根据什么文件生成的？我用GHS的MUTI_IDE编译生成的ELF进行debug，无法查看当前程序运行的调用栈，是需要补充什么文件吗?&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 26 Nov 2025 01:59:37 GMT</pubDate>
    <dc:creator>WeiCh</dc:creator>
    <dc:date>2025-11-26T01:59:37Z</dc:date>
    <item>
      <title>S32DS debug call stack</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/S32DS-debug-call-stack/m-p/2248765#M30699</link>
      <description>&lt;P&gt;&lt;SPAN&gt;在S32DS IDE的调试界面中，从右上角的&lt;/SPAN&gt;&lt;SPAN&gt;Debug&lt;/SPAN&gt;&lt;SPAN&gt;窗口，可以查看到当前程序运行的调用栈(&lt;/SPAN&gt;&lt;SPAN&gt;Call Stack&lt;/SPAN&gt;&lt;SPAN&gt;)；&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;这个调用栈是根据什么文件生成的？我用GHS的MUTI_IDE编译生成的ELF进行debug，无法查看当前程序运行的调用栈，是需要补充什么文件吗?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 26 Nov 2025 01:59:37 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/S32DS-debug-call-stack/m-p/2248765#M30699</guid>
      <dc:creator>WeiCh</dc:creator>
      <dc:date>2025-11-26T01:59:37Z</dc:date>
    </item>
    <item>
      <title>Re: S32DS debug call stack</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/S32DS-debug-call-stack/m-p/2250447#M30712</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;what's your S32DS version and target MCU?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 27 Nov 2025 14:02:48 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/S32DS-debug-call-stack/m-p/2250447#M30712</guid>
      <dc:creator>jiri_kral</dc:creator>
      <dc:date>2025-11-27T14:02:48Z</dc:date>
    </item>
    <item>
      <title>Re: S32DS debug call stack</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/S32DS-debug-call-stack/m-p/2250713#M30716</link>
      <description>V3.5 and 32K358</description>
      <pubDate>Fri, 28 Nov 2025 02:40:15 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/S32DS-debug-call-stack/m-p/2250713#M30716</guid>
      <dc:creator>WeiCh</dc:creator>
      <dc:date>2025-11-28T02:40:15Z</dc:date>
    </item>
    <item>
      <title>Re: S32DS debug call stack</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/S32DS-debug-call-stack/m-p/2308917#M31165</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;sorry for long delay. Unfortunately GHS is not fully compatible with Dwarf and if you are using GNU gdb client, it brings some issues. One of them may be missing call stack. It is known limitation for debugging GHS built .elf with GNU gdb client.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Feb 2026 14:34:33 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/S32DS-debug-call-stack/m-p/2308917#M31165</guid>
      <dc:creator>jiri_kral</dc:creator>
      <dc:date>2026-02-04T14:34:33Z</dc:date>
    </item>
  </channel>
</rss>

