<?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 core dump in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/core-dump/m-p/4253653#M331850</link>
    <description>Hi,&lt;BR /&gt;core dump. what is does mean &amp;amp; how do collect?&lt;BR /&gt;&lt;BR /&gt;Please help me to collect.&lt;BR /&gt;&lt;BR /&gt;Thanks;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Mon, 18 Aug 2008 06:40:31 GMT</pubDate>
    <dc:creator>txtraz</dc:creator>
    <dc:date>2008-08-18T06:40:31Z</dc:date>
    <item>
      <title>core dump</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/core-dump/m-p/4253653#M331850</link>
      <description>Hi,&lt;BR /&gt;core dump. what is does mean &amp;amp; how do collect?&lt;BR /&gt;&lt;BR /&gt;Please help me to collect.&lt;BR /&gt;&lt;BR /&gt;Thanks;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 18 Aug 2008 06:40:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/core-dump/m-p/4253653#M331850</guid>
      <dc:creator>txtraz</dc:creator>
      <dc:date>2008-08-18T06:40:31Z</dc:date>
    </item>
    <item>
      <title>Re: core dump</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/core-dump/m-p/4253654#M331851</link>
      <description>Hello,&lt;BR /&gt;The core dump file is collection of data when there is system crash due to lvm reason.Also it will keep the data which is lost.&lt;BR /&gt;If you had nickel script runnig on system,then just run that script and it will collect Core dump for you.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;The Guru.</description>
      <pubDate>Mon, 18 Aug 2008 07:31:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/core-dump/m-p/4253654#M331851</guid>
      <dc:creator>Gurudatta Shinde</dc:creator>
      <dc:date>2008-08-18T07:31:32Z</dc:date>
    </item>
    <item>
      <title>Re: core dump</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/core-dump/m-p/4253655#M331852</link>
      <description>check this link&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums12.itrc.hp.com/service/forums/questionanswer.do?threadId=40484" target="_blank"&gt;http://forums12.itrc.hp.com/service/forums/questionanswer.do?threadId=40484&lt;/A&gt;</description>
      <pubDate>Mon, 18 Aug 2008 07:35:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/core-dump/m-p/4253655#M331852</guid>
      <dc:creator>Jeeshan</dc:creator>
      <dc:date>2008-08-18T07:35:38Z</dc:date>
    </item>
    <item>
      <title>Re: core dump</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/core-dump/m-p/4253656#M331853</link>
      <description>Check out manpage of 'core':&lt;BR /&gt;&lt;BR /&gt;      The HP-UX system writes out a file containing a core image of a&lt;BR /&gt;      terminated process when certain signals are received (see signal(5)&lt;BR /&gt;      for the list of reasons).  The most common causes are memory&lt;BR /&gt;      violations, illegal instructions, floating point exceptions, bus&lt;BR /&gt;      errors, and user-generated quit signals.  The core image file is&lt;BR /&gt;      called core and is written in the process's working directory&lt;BR /&gt;      (provided it is allowed by normal access controls).  A process with an&lt;BR /&gt;      effective user ID different from its real user ID does not produce a&lt;BR /&gt;      core image.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 18 Aug 2008 07:56:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/core-dump/m-p/4253656#M331853</guid>
      <dc:creator>Venkatesh BL</dc:creator>
      <dc:date>2008-08-18T07:56:13Z</dc:date>
    </item>
    <item>
      <title>Re: core dump</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/core-dump/m-p/4253657#M331854</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;Core dumps vary a lot application to application.&lt;BR /&gt;&lt;BR /&gt;what they are is a dump of whatever was in memory when the program unexpectedly terminates.&lt;BR /&gt;&lt;BR /&gt;I've had reasonable results simply running the strings command against these things.&lt;BR /&gt;&lt;BR /&gt;When Oracle core dumps, oracle support can analyze the dump and figure out if their code is bad or system setup needs to be changed.&lt;BR /&gt;&lt;BR /&gt;So what to do and how useful it can be varies a lot, application to application.&lt;BR /&gt;&lt;BR /&gt;Not being a developer, I assume this is functionality you have to write into the application, or it comes from the compiler.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Mon, 18 Aug 2008 07:59:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/core-dump/m-p/4253657#M331854</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2008-08-18T07:59:38Z</dc:date>
    </item>
    <item>
      <title>Re: core dump</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/core-dump/m-p/4253658#M331855</link>
      <description>&amp;gt;what is does mean &amp;amp; how do collect?&lt;BR /&gt;&lt;BR /&gt;A core file is what you get if you don't have a signal handler for specific signals.&lt;BR /&gt;It captures the application's state at the time of the abort.  With a debugger, you can use the core file to query the variables, get a stack trace, etc.&lt;BR /&gt;&lt;BR /&gt;What do you mean by "collect"?  You want to hunt them down and remove them?  Or debug them?&lt;BR /&gt;&lt;BR /&gt;&amp;gt;SEP: I've had reasonable results simply running the strings command against these things.&lt;BR /&gt;&lt;BR /&gt;I would take that with a grain of salt.  Looking at random memory will may give you all possible error messages, not the reason for the abort.&lt;BR /&gt;Using file(1) and gdb to get a stack trace would be most helpful.&lt;BR /&gt;&lt;BR /&gt;&amp;gt;this is functionality you have to write into the application&lt;BR /&gt;&lt;BR /&gt;No, this is part of the kernel.  If you don't want a core file, you generally have to write extra code in the application.</description>
      <pubDate>Mon, 18 Aug 2008 11:54:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/core-dump/m-p/4253658#M331855</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2008-08-18T11:54:40Z</dc:date>
    </item>
    <item>
      <title>Re: core dump</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/core-dump/m-p/4253659#M331856</link>
      <description>Unless you are talking about a kernel crash or panic dump?&lt;BR /&gt;Those are in /var/adm/crash/.</description>
      <pubDate>Mon, 18 Aug 2008 12:22:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/core-dump/m-p/4253659#M331856</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2008-08-18T12:22:56Z</dc:date>
    </item>
    <item>
      <title>Re: core dump</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/core-dump/m-p/4253660#M331857</link>
      <description>You should contact various application support team to analys the core dumps.&lt;BR /&gt;For system core dumps you can contact HP, they will provide the support to you. For oracle dumps contact oracle.&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;&lt;BR /&gt;SKR</description>
      <pubDate>Mon, 18 Aug 2008 14:41:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/core-dump/m-p/4253660#M331857</guid>
      <dc:creator>SKR_1</dc:creator>
      <dc:date>2008-08-18T14:41:26Z</dc:date>
    </item>
  </channel>
</rss>

