<?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 PDGESVD segmentation fault in Intel® oneAPI Math Kernel Library</title>
    <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/PDGESVD-segmentation-fault/m-p/861055#M7517</link>
    <description>Hi,&lt;BR /&gt;I'm using PDGESVD, from scalapack in MKL, and sometimes it gives a segmentation fault. However, other times, it gives the right result. Are there any known bugs in PDGESVD that could cause this? This usually only happens for larger arrays, eg 16k x 16k or larger.&lt;BR /&gt;&lt;BR /&gt;I'm using it with openmpi.&lt;BR /&gt;&lt;BR /&gt;The following occurs while the call to pdgesvd is being computed.&lt;BR /&gt;[mc:08133] *** Process received signal ***&lt;BR /&gt;[mc:08133] Signal: Segmentation fault (11)&lt;BR /&gt;[mc:08133] Signal code: (-6)&lt;BR /&gt;[mc:08133] Failing at address: 0x1f400001fc5&lt;BR /&gt;[mc:08133] [ 0] /lib/libpthread.so.0 [0x2b8d4bb66100]&lt;BR /&gt;[mc:08133] [ 1] /lib/libpthread.so.0(raise+0x2b) [0x2b8d4bb65fcb]&lt;BR /&gt;[mc:08133] [ 2] /opt/intel/mkl/10.0.1.014/lib/em64t/libguide.so [0x2b8d4ba2a661]&lt;BR /&gt;&lt;BR /&gt;Thanks...&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Tue, 08 Jul 2008 11:49:21 GMT</pubDate>
    <dc:creator>Basden__Alastair</dc:creator>
    <dc:date>2008-07-08T11:49:21Z</dc:date>
    <item>
      <title>PDGESVD segmentation fault</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/PDGESVD-segmentation-fault/m-p/861055#M7517</link>
      <description>Hi,&lt;BR /&gt;I'm using PDGESVD, from scalapack in MKL, and sometimes it gives a segmentation fault. However, other times, it gives the right result. Are there any known bugs in PDGESVD that could cause this? This usually only happens for larger arrays, eg 16k x 16k or larger.&lt;BR /&gt;&lt;BR /&gt;I'm using it with openmpi.&lt;BR /&gt;&lt;BR /&gt;The following occurs while the call to pdgesvd is being computed.&lt;BR /&gt;[mc:08133] *** Process received signal ***&lt;BR /&gt;[mc:08133] Signal: Segmentation fault (11)&lt;BR /&gt;[mc:08133] Signal code: (-6)&lt;BR /&gt;[mc:08133] Failing at address: 0x1f400001fc5&lt;BR /&gt;[mc:08133] [ 0] /lib/libpthread.so.0 [0x2b8d4bb66100]&lt;BR /&gt;[mc:08133] [ 1] /lib/libpthread.so.0(raise+0x2b) [0x2b8d4bb65fcb]&lt;BR /&gt;[mc:08133] [ 2] /opt/intel/mkl/10.0.1.014/lib/em64t/libguide.so [0x2b8d4ba2a661]&lt;BR /&gt;&lt;BR /&gt;Thanks...&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 08 Jul 2008 11:49:21 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/PDGESVD-segmentation-fault/m-p/861055#M7517</guid>
      <dc:creator>Basden__Alastair</dc:creator>
      <dc:date>2008-07-08T11:49:21Z</dc:date>
    </item>
    <item>
      <title>Re: PDGESVD segmentation fault</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/PDGESVD-segmentation-fault/m-p/861056#M7518</link>
      <description>Hi,&lt;BR /&gt;perhaps someone more knowledgeable can comment for me...&lt;BR /&gt;Could this problem be down to using more than 2GB memory? &lt;BR /&gt;I have been linking with lp64 libraries, but maybe I should be using ilp64? &lt;BR /&gt;I'm using C, so is this as simple as changing my ints to MKL_INT and then compiling with -DMKL_ILP64 and linking to the ilp64 versions?&lt;BR /&gt;My current links are:&lt;BR /&gt;-lmkl_scalapack_lp64 -lmkl_blacs_openmpi_lp64 -lmkl_lapack -lmkl_intel_lp64 -lmkl_intel_thread -lmkl_core -lguide -lpthread&lt;BR /&gt;Do I just change these to ilp64? What abot eg mkl_lapack mkl_intel_thread mkl_core and guide?&lt;BR /&gt;&lt;BR /&gt;I use /opt/openmpi/bin/mpicc to do the compiling.&lt;BR /&gt;&lt;BR /&gt;Thanks...&lt;BR /&gt;</description>
      <pubDate>Tue, 08 Jul 2008 16:43:36 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/PDGESVD-segmentation-fault/m-p/861056#M7518</guid>
      <dc:creator>Basden__Alastair</dc:creator>
      <dc:date>2008-07-08T16:43:36Z</dc:date>
    </item>
    <item>
      <title>Re: PDGESVD segmentation fault</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/PDGESVD-segmentation-fault/m-p/861057#M7519</link>
      <description>If your int arrays need to exceed 8GB, then you must switch your int types to 64-bit, using mkl ilp64.</description>
      <pubDate>Tue, 08 Jul 2008 16:47:50 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/PDGESVD-segmentation-fault/m-p/861057#M7519</guid>
      <dc:creator>TimP</dc:creator>
      <dc:date>2008-07-08T16:47:50Z</dc:date>
    </item>
    <item>
      <title>Re: PDGESVD segmentation fault</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/PDGESVD-segmentation-fault/m-p/861058#M7520</link>
      <description>Hi,&lt;BR /&gt;I've moved my int types to MKL_INT, and recompiled with -DMKL_ILP64, using the *_ilp64 libraries. However, now the call to sl_init_ is crashing, giving:&lt;BR /&gt;[mac1:18030] *** Process received signal ***&lt;BR /&gt;[mac1:18030] Signal: Segmentation fault (11)&lt;BR /&gt;[mac1:18030] Signal code: Address not mapped (1)&lt;BR /&gt;[mac1:18030] Failing at address: 0x1100000000&lt;BR /&gt;&lt;BR /&gt;The 3 inputs are now type MKL_INT (and the crash still happens if they are int). Is this correct? I can't find sl_init in the header files anywhere... (though the library is in libmkl_scalapack_ilp64.a I think).&lt;BR /&gt;&lt;BR /&gt;It works fine with the lp64 version.&lt;BR /&gt;&lt;BR /&gt;Thanks...&lt;BR /&gt;</description>
      <pubDate>Wed, 09 Jul 2008 11:23:33 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/PDGESVD-segmentation-fault/m-p/861058#M7520</guid>
      <dc:creator>Basden__Alastair</dc:creator>
      <dc:date>2008-07-09T11:23:33Z</dc:date>
    </item>
  </channel>
</rss>

