<?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 Memory leak in SearchPath() for MKL 7.2.1 in Intel® oneAPI Math Kernel Library</title>
    <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Memory-leak-in-SearchPath-for-MKL-7-2-1/m-p/877142#M9073</link>
    <description>I was using MKL 7.2.1 on Linux Fedora 9 with EM64T architecture and discovered a memory leak in function SearchPath(), which is defined in the library em64t/libmkl_lapack.a. Here's how to reproduce the problem:&lt;BR /&gt;&lt;BR /&gt;1. Have program which uses MKL, for example:&lt;BR /&gt;===========program matinv&lt;BR /&gt; implicit none&lt;BR /&gt; external sgesv&lt;BR /&gt; real :: g3(2,2) = (/ 0d0, 1d0, 2d0, 3d0 /)&lt;BR /&gt; real :: gu3(2,2) = (/ 1d0, 0d0, 0d0, 1d0 /)&lt;BR /&gt; integer :: ipiv(2) = (/ 1, 2 /)&lt;BR /&gt; integer :: info&lt;BR /&gt; integer :: n=2, nrhs=2&lt;BR /&gt;&lt;BR /&gt; write (*,*) "Calling sgesv..."&lt;BR /&gt; call sgesv (n, nrhs, g3, n, ipiv, gu3, n, info)&lt;BR /&gt; write (*,*) "inv(g3) = ", gu3&lt;BR /&gt;&lt;BR /&gt;end program matinv&lt;BR /&gt;=============&lt;BR /&gt;&lt;BR /&gt;2. Compile it (I enforce static here to ensure independence of environment):&lt;BR /&gt;ifort -static matinv.F90 -L/usr/local/packages/numrel/opt/intel/mkl721/lib/em64t -lmkl_lapack -lmkl_em64t -lguide -lpthread -o matinv.x&lt;BR /&gt;&lt;BR /&gt;3. Have a long sophisticated PATH environment variable with repeated entries:&lt;BR /&gt;export PATH=$PATH:$PATH:$PATH&lt;BR /&gt;&lt;BR /&gt;4. Run the program:&lt;BR /&gt;./matinv.x&lt;BR /&gt; Calling sgesv...&lt;BR /&gt;forrtl: severe (174): SIGSEGV, segmentation fault occurred&lt;BR /&gt;Image PC Routine Line Source &lt;BR /&gt;matinv.x 0000000000402F29 Unknown Unknown Unknown&lt;BR /&gt;&lt;BR /&gt;Stack trace terminated abnormally.&lt;BR /&gt;&lt;BR /&gt;Debugger's backtrace shows that the error happens in function SearchPath(), which is a symbol in libmkl_lapack.a library. Initially, with much more compex example, I was getting a segmentation fault which looked like this:&lt;BR /&gt;p0_6279: p4_error: interrupt SIGSEGV: 11&lt;BR /&gt;&lt;BR /&gt;Debugger still shows problems in SearchPath, and this behaviour is affected by PATH variable in a strange way. I can't tell exactly what in my $PATH offends SearchPath function so much, whether it is repeated entries, or too many entries, or some special symbols. &lt;BR /&gt;&lt;BR /&gt;Is this fixed in later versions of MKL? Which version should I pick for my architecture? I tried 10.1.019, but probably it is not free for EM64T even for non-commercial usage, because my license file gets rejected with a message:&lt;BR /&gt;---&lt;BR /&gt;The license file(s) you provided is not valid for this product.&lt;BR /&gt;---&lt;BR /&gt;&lt;BR /&gt;Thanks.&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Thu, 19 Mar 2009 17:00:05 GMT</pubDate>
    <dc:creator>metamerik</dc:creator>
    <dc:date>2009-03-19T17:00:05Z</dc:date>
    <item>
      <title>Memory leak in SearchPath() for MKL 7.2.1</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Memory-leak-in-SearchPath-for-MKL-7-2-1/m-p/877142#M9073</link>
      <description>I was using MKL 7.2.1 on Linux Fedora 9 with EM64T architecture and discovered a memory leak in function SearchPath(), which is defined in the library em64t/libmkl_lapack.a. Here's how to reproduce the problem:&lt;BR /&gt;&lt;BR /&gt;1. Have program which uses MKL, for example:&lt;BR /&gt;===========program matinv&lt;BR /&gt; implicit none&lt;BR /&gt; external sgesv&lt;BR /&gt; real :: g3(2,2) = (/ 0d0, 1d0, 2d0, 3d0 /)&lt;BR /&gt; real :: gu3(2,2) = (/ 1d0, 0d0, 0d0, 1d0 /)&lt;BR /&gt; integer :: ipiv(2) = (/ 1, 2 /)&lt;BR /&gt; integer :: info&lt;BR /&gt; integer :: n=2, nrhs=2&lt;BR /&gt;&lt;BR /&gt; write (*,*) "Calling sgesv..."&lt;BR /&gt; call sgesv (n, nrhs, g3, n, ipiv, gu3, n, info)&lt;BR /&gt; write (*,*) "inv(g3) = ", gu3&lt;BR /&gt;&lt;BR /&gt;end program matinv&lt;BR /&gt;=============&lt;BR /&gt;&lt;BR /&gt;2. Compile it (I enforce static here to ensure independence of environment):&lt;BR /&gt;ifort -static matinv.F90 -L/usr/local/packages/numrel/opt/intel/mkl721/lib/em64t -lmkl_lapack -lmkl_em64t -lguide -lpthread -o matinv.x&lt;BR /&gt;&lt;BR /&gt;3. Have a long sophisticated PATH environment variable with repeated entries:&lt;BR /&gt;export PATH=$PATH:$PATH:$PATH&lt;BR /&gt;&lt;BR /&gt;4. Run the program:&lt;BR /&gt;./matinv.x&lt;BR /&gt; Calling sgesv...&lt;BR /&gt;forrtl: severe (174): SIGSEGV, segmentation fault occurred&lt;BR /&gt;Image PC Routine Line Source &lt;BR /&gt;matinv.x 0000000000402F29 Unknown Unknown Unknown&lt;BR /&gt;&lt;BR /&gt;Stack trace terminated abnormally.&lt;BR /&gt;&lt;BR /&gt;Debugger's backtrace shows that the error happens in function SearchPath(), which is a symbol in libmkl_lapack.a library. Initially, with much more compex example, I was getting a segmentation fault which looked like this:&lt;BR /&gt;p0_6279: p4_error: interrupt SIGSEGV: 11&lt;BR /&gt;&lt;BR /&gt;Debugger still shows problems in SearchPath, and this behaviour is affected by PATH variable in a strange way. I can't tell exactly what in my $PATH offends SearchPath function so much, whether it is repeated entries, or too many entries, or some special symbols. &lt;BR /&gt;&lt;BR /&gt;Is this fixed in later versions of MKL? Which version should I pick for my architecture? I tried 10.1.019, but probably it is not free for EM64T even for non-commercial usage, because my license file gets rejected with a message:&lt;BR /&gt;---&lt;BR /&gt;The license file(s) you provided is not valid for this product.&lt;BR /&gt;---&lt;BR /&gt;&lt;BR /&gt;Thanks.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 19 Mar 2009 17:00:05 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Memory-leak-in-SearchPath-for-MKL-7-2-1/m-p/877142#M9073</guid>
      <dc:creator>metamerik</dc:creator>
      <dc:date>2009-03-19T17:00:05Z</dc:date>
    </item>
    <item>
      <title>Re: Memory leak in SearchPath() for MKL 7.2.1</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Memory-leak-in-SearchPath-for-MKL-7-2-1/m-p/877143#M9074</link>
      <description>Just installed MKL 9,1.023 and the problem disappeared.&lt;BR /&gt;</description>
      <pubDate>Thu, 19 Mar 2009 17:33:16 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Memory-leak-in-SearchPath-for-MKL-7-2-1/m-p/877143#M9074</guid>
      <dc:creator>metamerik</dc:creator>
      <dc:date>2009-03-19T17:33:16Z</dc:date>
    </item>
  </channel>
</rss>

