<?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 Re: Segmentation fault during g2d_blit in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Segmentation-fault-during-g2d-blit/m-p/1883560#M224695</link>
    <description>&lt;BLOCKQUOTE&gt;&lt;P&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;g2d frame buffer is full.&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;Thanks. You mentioned that g2d frame buffer is full. In what situations this g2d frame buffer gets full?&lt;/P&gt;</description>
    <pubDate>Fri, 07 Jun 2024 11:26:14 GMT</pubDate>
    <dc:creator>marko1921</dc:creator>
    <dc:date>2024-06-07T11:26:14Z</dc:date>
    <item>
      <title>Segmentation fault during g2d_blit</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Segmentation-fault-during-g2d-blit/m-p/1881633#M224591</link>
      <description>&lt;P&gt;/usr/lib/libGAL.so(gco2D_SetYUVColorMode+0x70)[0xffff7b9e38f0]&lt;BR /&gt;/usr/lib/libg2d.so.1.5(g2d_blitEx+0xdcc)[0xffff7ed73904]&lt;BR /&gt;/usr/lib/libg2d.so.1.5(g2d_blit+0x90)[0xffff7ed742b8]&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Sometimes g2d_blit function throws sementation fauld with above stack trace&lt;BR /&gt;Could you please help to find root cause. Usually my code works fine but sometimes it throws seg fault.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 05 Jun 2024 16:10:48 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Segmentation-fault-during-g2d-blit/m-p/1881633#M224591</guid>
      <dc:creator>marko1921</dc:creator>
      <dc:date>2024-06-05T16:10:48Z</dc:date>
    </item>
    <item>
      <title>Re: Segmentation fault during g2d_blit</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Segmentation-fault-during-g2d-blit/m-p/1882845#M224656</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;The software has attempted to access a restricted area of memory, check your dtb appears the g2d frame buffer is full.&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Thu, 06 Jun 2024 14:50:31 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Segmentation-fault-during-g2d-blit/m-p/1882845#M224656</guid>
      <dc:creator>Bio_TICFSL</dc:creator>
      <dc:date>2024-06-06T14:50:31Z</dc:date>
    </item>
    <item>
      <title>Re: Segmentation fault during g2d_blit</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Segmentation-fault-during-g2d-blit/m-p/1883560#M224695</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;P&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;g2d frame buffer is full.&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;Thanks. You mentioned that g2d frame buffer is full. In what situations this g2d frame buffer gets full?&lt;/P&gt;</description>
      <pubDate>Fri, 07 Jun 2024 11:26:14 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Segmentation-fault-during-g2d-blit/m-p/1883560#M224695</guid>
      <dc:creator>marko1921</dc:creator>
      <dc:date>2024-06-07T11:26:14Z</dc:date>
    </item>
  </channel>
</rss>

