<?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: mlib 8.3 core dump in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/mlib-8-3-core-dump/m-p/2775563#M722374</link>
    <description>I don't know about the mlib thing, but as this happened just after an upgrade I would suggest findout out what patch matrix is required for *that version* of mlib, and checking you have the latest patches. I've tripped over that problem in java often enough ;-)&lt;BR /&gt;&lt;BR /&gt;Cheers!&lt;BR /&gt;James</description>
    <pubDate>Tue, 30 Jul 2002 12:43:47 GMT</pubDate>
    <dc:creator>James Beamish-White</dc:creator>
    <dc:date>2002-07-30T12:43:47Z</dc:date>
    <item>
      <title>mlib 8.3 core dump</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mlib-8-3-core-dump/m-p/2775562#M722373</link>
      <description>I have a program which uses the sparse matrix solver in mlib. It works fine with mlib version 8.1. However, after I updated the mlib to version 8.3, I got a core dump when "dslevm()" is called for the symmetric matrix. The error message "SIGSEGV, Segmentation fault" was from "cxd_dinpnv()" which was called by "dslevm()".&lt;BR /&gt;&lt;BR /&gt;Any help is appreciated.&lt;BR /&gt;&lt;BR /&gt;Dong Zheng</description>
      <pubDate>Tue, 30 Jul 2002 12:40:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mlib-8-3-core-dump/m-p/2775562#M722373</guid>
      <dc:creator>Dong Zheng</dc:creator>
      <dc:date>2002-07-30T12:40:37Z</dc:date>
    </item>
    <item>
      <title>Re: mlib 8.3 core dump</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mlib-8-3-core-dump/m-p/2775563#M722374</link>
      <description>I don't know about the mlib thing, but as this happened just after an upgrade I would suggest findout out what patch matrix is required for *that version* of mlib, and checking you have the latest patches. I've tripped over that problem in java often enough ;-)&lt;BR /&gt;&lt;BR /&gt;Cheers!&lt;BR /&gt;James</description>
      <pubDate>Tue, 30 Jul 2002 12:43:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mlib-8-3-core-dump/m-p/2775563#M722374</guid>
      <dc:creator>James Beamish-White</dc:creator>
      <dc:date>2002-07-30T12:43:47Z</dc:date>
    </item>
  </channel>
</rss>

