<?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 Shared Memory Corruption in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/shared-memory-corruption/m-p/2863066#M96696</link>
    <description>I have a server running 10.20 with one of our in house applications.&lt;BR /&gt;The application is suffering from what appears to be some kind of shared memory corruption.&lt;BR /&gt;I collected shared memory dumps periodically, and if I run 'xd -c &lt;FILENAME&gt;' I see the following entries where the contents cannot be converted into ASCII characters:0000e30                            ff ff ff ff ff ff ff&lt;BR /&gt;0000e40 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff&lt;BR /&gt;&lt;BR /&gt;Has anybody seen this kind of thing before?&lt;BR /&gt;Does it look like shared memory is corrupt or is it more likely that the application is sending the bad data in the first place?&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/FILENAME&gt;</description>
    <pubDate>Thu, 12 Dec 2002 11:29:38 GMT</pubDate>
    <dc:creator>John Walker_1</dc:creator>
    <dc:date>2002-12-12T11:29:38Z</dc:date>
    <item>
      <title>Shared Memory Corruption</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/shared-memory-corruption/m-p/2863066#M96696</link>
      <description>I have a server running 10.20 with one of our in house applications.&lt;BR /&gt;The application is suffering from what appears to be some kind of shared memory corruption.&lt;BR /&gt;I collected shared memory dumps periodically, and if I run 'xd -c &lt;FILENAME&gt;' I see the following entries where the contents cannot be converted into ASCII characters:0000e30                            ff ff ff ff ff ff ff&lt;BR /&gt;0000e40 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff&lt;BR /&gt;&lt;BR /&gt;Has anybody seen this kind of thing before?&lt;BR /&gt;Does it look like shared memory is corrupt or is it more likely that the application is sending the bad data in the first place?&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/FILENAME&gt;</description>
      <pubDate>Thu, 12 Dec 2002 11:29:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/shared-memory-corruption/m-p/2863066#M96696</guid>
      <dc:creator>John Walker_1</dc:creator>
      <dc:date>2002-12-12T11:29:38Z</dc:date>
    </item>
    <item>
      <title>Re: Shared Memory Corruption</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/shared-memory-corruption/m-p/2863067#M96697</link>
      <description>&lt;BR /&gt;Run stm. If nothing is reported, have the developers fix their code, and in the mean time get them to start porting to 11i, as you only have 6 more months left!&lt;BR /&gt;&lt;BR /&gt;live free or die&lt;BR /&gt;harry</description>
      <pubDate>Thu, 12 Dec 2002 11:59:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/shared-memory-corruption/m-p/2863067#M96697</guid>
      <dc:creator>harry d brown jr</dc:creator>
      <dc:date>2002-12-12T11:59:33Z</dc:date>
    </item>
  </channel>
</rss>

