1 Reply Latest reply on Mar 13, 2017 6:43 AM by vikiz

    VMA error

    cocotr

      Hello,

      I get segmentation fault on SLES using LD_PRELOAD=libvma.so . I don't have this problem using Centos/RHEL

       

      VMA ERROR: Segmentation Fault

      [tid: 23416] ------ printf_backtrace ------

      [1] 0x7fe4c5330e1c: /usr/lib64/libvma.so:()

      [2] 0x7fe4c2cce046: /opt/dotnet/shared/Microsoft.NETCore.App/1.1.1/libcoreclr.so:()

      [3] 0x7fddcc5045b6: /opt/dotnet/shared/Microsoft.NETCore.App/1.1.1/libclrjit.so:()

      [4] 0x7fe4c4e29870: /lib64/libpthread.so.0:()

      [5] 0x7fe4c529d90b: /usr/lib64/libvma.so:ring_allocation_logic::should_migrate_ring()

      [6] 0x7fe4c52ed8a8: /usr/lib64/libvma.so:dst_entry::try_migrate_ring(lock_base&)

      [7] 0x7fe4c530a7b8: /usr/lib64/libvma.so:sockinfo_tcp::ip_output(pbuf*, void*, int)

      [8] 0x7fe4c52d0212: /usr/lib64/libvma.so:tcp_output()

      [9] 0x7fe4c52cc999: /usr/lib64/libvma.so:tcp_slowtmr()

      Killed

        • Re: VMA error
          vikiz

          Hi Oskar,

           

          There are several things that can cause a Segmentation Fault:

           

          1. Which application you are trying to run with libvma.so?

          Note that Netcat with VMA on SLES 11 SP1 does not function.

           

          2. There is also a known NetPIPE bug - Netpipe is trying to access read-only memory and there is Segmentation fault on NetPIPE exit- the solution is to upgrade to NetPIPE 3.7 or later.

           

          3. Directing VMA to access non-valid memory area will cause a segmentation fault.

           

          4. There was a segmentation fault issue in vma_stats when exceeding fds string length that was discovered in 8.0.4 and was fixed in VMA 8.1.7.

           

          5. There was a segmentation fault issue when running with CTL_THREAD_NO_WAKEUP - was discovered in 8.0.4 and was fixed in VMA 8.1.7.

           

          Regards,

          Viki