<?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: ERROR MESSAGE : Cannot access memory at address 0x3f 5d0268; Language : C++ in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/error-message-cannot-access-memory-at-address-0x3f-5d0268/m-p/2856061#M721469</link>
    <description>Hi.&lt;BR /&gt;&lt;BR /&gt;What does exactly backtrace of the stack, when your process gets killed inside malloc? What signal kills the process?&lt;BR /&gt;&lt;BR /&gt;If it's from malloc my first guess is that you corrupt memory somewhere. Try to use a tool to trace memory allocations and overwriting. Perheps you are using freed memory, or write after / before allocated block, corrupting malloc's free list.&lt;BR /&gt;&lt;BR /&gt;Good luck&lt;BR /&gt;&lt;BR /&gt;Adam&lt;BR /&gt;</description>
    <pubDate>Tue, 03 Dec 2002 13:05:53 GMT</pubDate>
    <dc:creator>Adam J Markiewicz</dc:creator>
    <dc:date>2002-12-03T13:05:53Z</dc:date>
    <item>
      <title>ERROR MESSAGE : Cannot access memory at address 0x3f 5d0268; Language : C++</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/error-message-cannot-access-memory-at-address-0x3f-5d0268/m-p/2856059#M721467</link>
      <description>Hi wizards,&lt;BR /&gt;&lt;BR /&gt;We have a Wireless application [GSM] in which we have wriiten the code in C++ Lang on a HP-UX 10.20 platform and the Target HP Hardware is N-Class servers.&lt;BR /&gt;&lt;BR /&gt;It's been reported that our application is coring sometimes. &lt;BR /&gt;&lt;BR /&gt;And from the gdb traces, we see a line as:&lt;BR /&gt;~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~&lt;BR /&gt;"Cannot access memory at address 0x3f 5d0268"  and then it gets killed in malloc...&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Please help me out in this regard.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Thanks in Advance,&lt;BR /&gt;Arun Kumar &lt;BR /&gt;Bangalore, INDIA.&lt;BR /&gt; &lt;BR /&gt; &lt;BR /&gt; &lt;BR /&gt;</description>
      <pubDate>Tue, 03 Dec 2002 06:39:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/error-message-cannot-access-memory-at-address-0x3f-5d0268/m-p/2856059#M721467</guid>
      <dc:creator>arun kumar v</dc:creator>
      <dc:date>2002-12-03T06:39:00Z</dc:date>
    </item>
    <item>
      <title>Re: ERROR MESSAGE : Cannot access memory at address 0x3f 5d0268; Language : C++</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/error-message-cannot-access-memory-at-address-0x3f-5d0268/m-p/2856060#M721468</link>
      <description>Arun,&lt;BR /&gt;are you sure you have 1GB of the main memory and at this location (0x3f5d0268=1,063,060,072) server does not have memory hole, ROM or any other locked area? If your server is out-of-memory then consider (at least try) to add more&lt;BR /&gt;Eugeny</description>
      <pubDate>Tue, 03 Dec 2002 08:06:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/error-message-cannot-access-memory-at-address-0x3f-5d0268/m-p/2856060#M721468</guid>
      <dc:creator>Eugeny Brychkov</dc:creator>
      <dc:date>2002-12-03T08:06:42Z</dc:date>
    </item>
    <item>
      <title>Re: ERROR MESSAGE : Cannot access memory at address 0x3f 5d0268; Language : C++</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/error-message-cannot-access-memory-at-address-0x3f-5d0268/m-p/2856061#M721469</link>
      <description>Hi.&lt;BR /&gt;&lt;BR /&gt;What does exactly backtrace of the stack, when your process gets killed inside malloc? What signal kills the process?&lt;BR /&gt;&lt;BR /&gt;If it's from malloc my first guess is that you corrupt memory somewhere. Try to use a tool to trace memory allocations and overwriting. Perheps you are using freed memory, or write after / before allocated block, corrupting malloc's free list.&lt;BR /&gt;&lt;BR /&gt;Good luck&lt;BR /&gt;&lt;BR /&gt;Adam&lt;BR /&gt;</description>
      <pubDate>Tue, 03 Dec 2002 13:05:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/error-message-cannot-access-memory-at-address-0x3f-5d0268/m-p/2856061#M721469</guid>
      <dc:creator>Adam J Markiewicz</dc:creator>
      <dc:date>2002-12-03T13:05:53Z</dc:date>
    </item>
  </channel>
</rss>

