<?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: MemorySanitizer:DEADLYSIGNAL when compiling for runtime debug using mpiifx in Intel® MPI Library</title>
    <link>https://community.intel.com/t5/Intel-MPI-Library/MemorySanitizer-DEADLYSIGNAL-when-compiling-for-runtime-debug/m-p/1567942#M11506</link>
    <description>&lt;P&gt;Thanks for the update&amp;nbsp;&lt;a href="https://community.intel.com/t5/user/viewprofilepage/user-id/245425"&gt;@TobiasK&lt;/a&gt;&amp;nbsp;, I will inform my team so they update their makefiles.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 31 Jan 2024 15:16:27 GMT</pubDate>
    <dc:creator>Mus</dc:creator>
    <dc:date>2024-01-31T15:16:27Z</dc:date>
    <item>
      <title>MemorySanitizer:DEADLYSIGNAL when compiling for runtime debug using mpiifx</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/MemorySanitizer-DEADLYSIGNAL-when-compiling-for-runtime-debug/m-p/1566953#M11483</link>
      <description>&lt;P&gt;Hello All,&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am using Intel OneAPI 2024, and I noticed when compiling in check using:&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="bash"&gt;-C -g -check -assume byterecl -check all -gen-interfaces -traceback -assume byterecl -fpe0 -qopenmp $(OPTPRE) -warn nostderrors&lt;/LI-CODE&gt;&lt;P&gt;(OPTPRE: is some pre-processing command)&lt;/P&gt;&lt;P&gt;with mpiifx I get the following error on runtime, before any output from the program itself:&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="bash"&gt;MemorySanitizer:DEADLYSIGNAL
==22054==ERROR: MemorySanitizer: SEGV on unknown address 0x000000000413 (pc 0x000000000413 bp 0x7fff50f50a55 sp 0x7fff50f509a8 T22054)
==22054==Hint: pc points to the zero page.
==22054==The signal is caused by a READ memory access.
==22054==Hint: address points to the zero page.
MemorySanitizer:DEADLYSIGNAL
MemorySanitizer: nested bug in the same thread, aborting.&lt;/LI-CODE&gt;&lt;P&gt;&lt;FONT size="3"&gt;Compiling with mpiifort, does not give rise to this error. &lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT size="3"&gt;I have noticed this recently just after I updated to Intel OneAPI 2024.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am not trying to debug my code, I am just wondering if this is expected behavior, and if so, how would I interpret this message to fix the error?&amp;nbsp;&lt;/P&gt;&lt;P&gt;PS: with mpiifort the runtime debug is running normally as before I upgraded.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you and have a lovely day.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Mus&lt;/P&gt;</description>
      <pubDate>Mon, 29 Jan 2024 08:28:56 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/MemorySanitizer-DEADLYSIGNAL-when-compiling-for-runtime-debug/m-p/1566953#M11483</guid>
      <dc:creator>Mus</dc:creator>
      <dc:date>2024-01-29T08:28:56Z</dc:date>
    </item>
    <item>
      <title>Re: MemorySanitizer:DEADLYSIGNAL when compiling for runtime debug using mpiifx</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/MemorySanitizer-DEADLYSIGNAL-when-compiling-for-runtime-debug/m-p/1567090#M11484</link>
      <description>&lt;P&gt;I'll move this to the &lt;A href="https://community.intel.com/t5/Intel-HPC-Toolkit/bd-p/oneapi-hpc-toolkit" target="_blank" rel="noopener"&gt;HPC Toolkit Forum&lt;/A&gt;. That forum is best for MPI issues.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 29 Jan 2024 15:39:58 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/MemorySanitizer-DEADLYSIGNAL-when-compiling-for-runtime-debug/m-p/1567090#M11484</guid>
      <dc:creator>Barbara_P_Intel</dc:creator>
      <dc:date>2024-01-29T15:39:58Z</dc:date>
    </item>
    <item>
      <title>Re:MemorySanitizer:DEADLYSIGNAL when compiling for runtime debug using mpiifx</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/MemorySanitizer-DEADLYSIGNAL-when-compiling-for-runtime-debug/m-p/1567881#M11497</link>
      <description>&lt;P&gt;&lt;a href="https://community.intel.com/t5/user/viewprofilepage/user-id/337559"&gt;@Mus&lt;/a&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;please add -check all,nouninit for the time being (also please note your compilation line contains -C -check and -check all which is redundant...)&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;I will have to check with the compiler team how to avoid that.&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 31 Jan 2024 12:00:35 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/MemorySanitizer-DEADLYSIGNAL-when-compiling-for-runtime-debug/m-p/1567881#M11497</guid>
      <dc:creator>TobiasK</dc:creator>
      <dc:date>2024-01-31T12:00:35Z</dc:date>
    </item>
    <item>
      <title>Re: MemorySanitizer:DEADLYSIGNAL when compiling for runtime debug using mpiifx</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/MemorySanitizer-DEADLYSIGNAL-when-compiling-for-runtime-debug/m-p/1567884#M11498</link>
      <description>&lt;P&gt;&lt;a href="https://community.intel.com/t5/user/viewprofilepage/user-id/245425"&gt;@TobiasK&lt;/a&gt;&amp;nbsp; Thank you for the reply.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Adding the nouninit flag seemed to have solved the issue. I'm gonna go ahead and mark this as solved.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 31 Jan 2024 12:04:45 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/MemorySanitizer-DEADLYSIGNAL-when-compiling-for-runtime-debug/m-p/1567884#M11498</guid>
      <dc:creator>Mus</dc:creator>
      <dc:date>2024-01-31T12:04:45Z</dc:date>
    </item>
    <item>
      <title>Re:MemorySanitizer:DEADLYSIGNAL when compiling for runtime debug using mpiifx</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/MemorySanitizer-DEADLYSIGNAL-when-compiling-for-runtime-debug/m-p/1567916#M11504</link>
      <description>&lt;P&gt;&lt;a href="https://community.intel.com/t5/user/viewprofilepage/user-id/337559"&gt;@Mus&lt;/a&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Ron updated his 'Known bug post'&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.intel.com/t5/Intel-Fortran-Compiler/Known-bug-with-check-all-or-check-uninit-in-ifx-2024-0-0-for/m-p/1545825" target="_blank"&gt;https://community.intel.com/t5/Intel-Fortran-Compiler/Known-bug-with-check-all-or-check-uninit-in-ifx-2024-0-0-for/m-p/1545825&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;For the time being, -check uninit will not work with either MPI nor MKL. Unfortunately, uninit is part of check all for now. &lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 31 Jan 2024 14:25:16 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/MemorySanitizer-DEADLYSIGNAL-when-compiling-for-runtime-debug/m-p/1567916#M11504</guid>
      <dc:creator>TobiasK</dc:creator>
      <dc:date>2024-01-31T14:25:16Z</dc:date>
    </item>
    <item>
      <title>Re: MemorySanitizer:DEADLYSIGNAL when compiling for runtime debug using mpiifx</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/MemorySanitizer-DEADLYSIGNAL-when-compiling-for-runtime-debug/m-p/1567942#M11506</link>
      <description>&lt;P&gt;Thanks for the update&amp;nbsp;&lt;a href="https://community.intel.com/t5/user/viewprofilepage/user-id/245425"&gt;@TobiasK&lt;/a&gt;&amp;nbsp;, I will inform my team so they update their makefiles.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 31 Jan 2024 15:16:27 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/MemorySanitizer-DEADLYSIGNAL-when-compiling-for-runtime-debug/m-p/1567942#M11506</guid>
      <dc:creator>Mus</dc:creator>
      <dc:date>2024-01-31T15:16:27Z</dc:date>
    </item>
  </channel>
</rss>

