<?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>topic Debugging Issue on imx6UL in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Debugging-Issue-on-imx6UL/m-p/630159#M95674</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello all,&lt;/P&gt;&lt;P&gt;We have a Qt based application and it compiles and runs successfully on target board. However, when we try to debug the application, SEGV signal got from the application and application stops running. Below please find the output:&lt;/P&gt;&lt;P&gt;0x76fcfac0 in ?? () from /toolchain/sysroots/cortexa7hf-vfp-neon-dey-linux-gnueabi/lib/ld-linux-armhf.so.3&lt;BR /&gt;The target endianness is set automatically (currently little endian)&lt;/P&gt;&lt;P&gt;Program received signal SIGSEGV, Segmentation fault.&lt;BR /&gt;0x76fdfa98 in ?? () from /toolchain/sysroots/cortexa7hf-vfp-neon-dey-linux-gnueabi/lib/ld-linux-armhf.so.3&lt;/P&gt;&lt;P&gt;To debug the application, we start the gdbserver in target platform and we simply start the gdb (compiled within the cross tool chain).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However the same application runs without any problems when we simply run the application from the console.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please find below the used Ecplise debugger settings for debugging the application:&lt;/P&gt;&lt;P&gt;GDB Debugger: /toolchain/sysroots/x86_64-deysdk-linux/usr/bin/arm-dey-linux-gnueabi/arm-dey-linux-gnueabi-gdb&lt;/P&gt;&lt;P&gt;GDB Command Line: (Below is the file content)&lt;/P&gt;&lt;P&gt;set sysroot /toolchain/sysroots/cortexa7hf-vfp-neon-dey-linux-gnueabi&lt;BR /&gt;set auto-load safe-path /&lt;/P&gt;&lt;P&gt;Using GDB (DSF) Manual Remote Debugger Launcher&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Why there is such problem?&lt;/P&gt;&lt;P&gt;Sincerely.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 07 Mar 2017 13:17:05 GMT</pubDate>
    <dc:creator>enginfirat</dc:creator>
    <dc:date>2017-03-07T13:17:05Z</dc:date>
    <item>
      <title>Debugging Issue on imx6UL</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Debugging-Issue-on-imx6UL/m-p/630159#M95674</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello all,&lt;/P&gt;&lt;P&gt;We have a Qt based application and it compiles and runs successfully on target board. However, when we try to debug the application, SEGV signal got from the application and application stops running. Below please find the output:&lt;/P&gt;&lt;P&gt;0x76fcfac0 in ?? () from /toolchain/sysroots/cortexa7hf-vfp-neon-dey-linux-gnueabi/lib/ld-linux-armhf.so.3&lt;BR /&gt;The target endianness is set automatically (currently little endian)&lt;/P&gt;&lt;P&gt;Program received signal SIGSEGV, Segmentation fault.&lt;BR /&gt;0x76fdfa98 in ?? () from /toolchain/sysroots/cortexa7hf-vfp-neon-dey-linux-gnueabi/lib/ld-linux-armhf.so.3&lt;/P&gt;&lt;P&gt;To debug the application, we start the gdbserver in target platform and we simply start the gdb (compiled within the cross tool chain).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However the same application runs without any problems when we simply run the application from the console.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please find below the used Ecplise debugger settings for debugging the application:&lt;/P&gt;&lt;P&gt;GDB Debugger: /toolchain/sysroots/x86_64-deysdk-linux/usr/bin/arm-dey-linux-gnueabi/arm-dey-linux-gnueabi-gdb&lt;/P&gt;&lt;P&gt;GDB Command Line: (Below is the file content)&lt;/P&gt;&lt;P&gt;set sysroot /toolchain/sysroots/cortexa7hf-vfp-neon-dey-linux-gnueabi&lt;BR /&gt;set auto-load safe-path /&lt;/P&gt;&lt;P&gt;Using GDB (DSF) Manual Remote Debugger Launcher&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Why there is such problem?&lt;/P&gt;&lt;P&gt;Sincerely.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 Mar 2017 13:17:05 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Debugging-Issue-on-imx6UL/m-p/630159#M95674</guid>
      <dc:creator>enginfirat</dc:creator>
      <dc:date>2017-03-07T13:17:05Z</dc:date>
    </item>
    <item>
      <title>Re: Debugging Issue on imx6UL</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Debugging-Issue-on-imx6UL/m-p/630160#M95675</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Engin&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;please check AN5229 ARM DS-5 Development Studio Debug i.MX6UL-EVK&lt;BR /&gt;&lt;A class="jive-link-external-small" href="https://community.nxp.com/external-link.jspa?url=http%3A%2F%2Fwww.nxp.com%2Fassets%2Fdocuments%2Fdata%2Fen%2Fapplication-notes%2FAN5229.pdf" rel="nofollow" target="_blank"&gt;http://www.nxp.com/assets/documents/data/en/application-notes/AN5229.pdf&lt;/A&gt;&lt;BR /&gt;AN4553 Using Open Source Debugging Tools for Linux on i.MX Processors&lt;BR /&gt;&lt;A href="http://www.nxp.com/assets/documents/data/en/application-notes/AN4553.pdf"&gt;http://www.nxp.com/assets/documents/data/en/application-notes/AN4553.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;BR /&gt;igor&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>Wed, 08 Mar 2017 00:00:43 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Debugging-Issue-on-imx6UL/m-p/630160#M95675</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2017-03-08T00:00:43Z</dc:date>
    </item>
    <item>
      <title>Re: Debugging Issue on imx6UL</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Debugging-Issue-on-imx6UL/m-p/630161#M95676</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Igor,&lt;/P&gt;&lt;P&gt;Actually, I setup an environment like mentioned in Document&amp;nbsp;AN4553 Using Open Source Debugging Tools for Linux on i.MX Processors. However as I have mentioned, whenever the debugging starts immediately SIGSEGV is thrown and debugging stops. Program does not break at any break point.&lt;/P&gt;&lt;P&gt;Sincerely.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 08 Mar 2017 09:21:18 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Debugging-Issue-on-imx6UL/m-p/630161#M95676</guid>
      <dc:creator>enginfirat</dc:creator>
      <dc:date>2017-03-08T09:21:18Z</dc:date>
    </item>
    <item>
      <title>Re: Debugging Issue on imx6UL</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Debugging-Issue-on-imx6UL/m-p/630162#M95677</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Engin&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;is it working without Qt, just linux.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;BR /&gt;igor&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 08 Mar 2017 11:27:47 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Debugging-Issue-on-imx6UL/m-p/630162#M95677</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2017-03-08T11:27:47Z</dc:date>
    </item>
    <item>
      <title>Re: Debugging Issue on imx6UL</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Debugging-Issue-on-imx6UL/m-p/630163#M95678</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Igor,&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have tried with two simple projects, one with Qt and one without Qt. For both tries, I was able to debug the application without any&amp;nbsp;problems.&lt;/P&gt;&lt;P&gt;As an another try, I have moved the application to QtCreator IDE and built and compiled it. The debugging attempt with Qt also produces a SIGSEGV however this time I was able to see where the executable access to invalid memory. Please see the attached screenshots:&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="SEGV.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/17731iC5F826B7C418123B/image-size/large?v=v2&amp;amp;px=999" role="button" title="SEGV.png" alt="SEGV.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="dl_debug_source.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/17779i6234F8A36A5730FA/image-size/large?v=v2&amp;amp;px=999" role="button" title="dl_debug_source.png" alt="dl_debug_source.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;(Ps. Above the line 55 is where the cursor hangs)&lt;/P&gt;&lt;P&gt;After a little search on problem I have found a stackoverflow thread:&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="http://stackoverflow.com/questions/42256374/segmentation-fault-only-during-gdb-debugging" title="http://stackoverflow.com/questions/42256374/segmentation-fault-only-during-gdb-debugging"&gt;boost - Segmentation fault only during GDB debugging - Stack Overflow&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Were you or any people from community faced this problem before? What is your opinion about the problem?&lt;/P&gt;&lt;P&gt;Sincerely.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 10 Mar 2017 13:49:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Debugging-Issue-on-imx6UL/m-p/630163#M95678</guid>
      <dc:creator>enginfirat</dc:creator>
      <dc:date>2017-03-10T13:49:49Z</dc:date>
    </item>
  </channel>
</rss>

