<?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: view core dump in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/view-core-dump/m-p/2713719#M721641</link>
    <description>Well, if "file core" or "strings core" gives you the info you need, you need not venture any further.&lt;BR /&gt;But if you need to backtrace to the line of code that caused the core dump, then you'll need a debugger like gdb, xdb or adb. There should be some threads in this forum dealing with the usage of debuggers.</description>
    <pubDate>Tue, 30 Apr 2002 02:38:24 GMT</pubDate>
    <dc:creator>Deepak Extross</dc:creator>
    <dc:date>2002-04-30T02:38:24Z</dc:date>
    <item>
      <title>view core dump</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/view-core-dump/m-p/2713717#M721639</link>
      <description>how to find out the cause of of core dump, by just viewing the "core" file? should I use any tools ? or simply use "strings core" for viewing those text... ?or should I should gdb for better debuging...?&lt;BR /&gt;&lt;BR /&gt;dummy developer</description>
      <pubDate>Tue, 30 Apr 2002 02:27:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/view-core-dump/m-p/2713717#M721639</guid>
      <dc:creator>cch_1</dc:creator>
      <dc:date>2002-04-30T02:27:28Z</dc:date>
    </item>
    <item>
      <title>Re: view core dump</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/view-core-dump/m-p/2713718#M721640</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;In addition, &lt;BR /&gt;&lt;BR /&gt;# file core&lt;BR /&gt;&lt;BR /&gt;If it is a system crash dump, use q4.&lt;BR /&gt;&lt;BR /&gt;Hope this helps. Regards.&lt;BR /&gt;&lt;BR /&gt;Steven Sim Kok Leong</description>
      <pubDate>Tue, 30 Apr 2002 02:31:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/view-core-dump/m-p/2713718#M721640</guid>
      <dc:creator>Steven Sim Kok Leong</dc:creator>
      <dc:date>2002-04-30T02:31:45Z</dc:date>
    </item>
    <item>
      <title>Re: view core dump</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/view-core-dump/m-p/2713719#M721641</link>
      <description>Well, if "file core" or "strings core" gives you the info you need, you need not venture any further.&lt;BR /&gt;But if you need to backtrace to the line of code that caused the core dump, then you'll need a debugger like gdb, xdb or adb. There should be some threads in this forum dealing with the usage of debuggers.</description>
      <pubDate>Tue, 30 Apr 2002 02:38:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/view-core-dump/m-p/2713719#M721641</guid>
      <dc:creator>Deepak Extross</dc:creator>
      <dc:date>2002-04-30T02:38:24Z</dc:date>
    </item>
    <item>
      <title>Re: view core dump</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/view-core-dump/m-p/2713720#M721642</link>
      <description>I would definitely use 'file core' over strings, as the latter will give you all the "standard text" as well. That will give you the name of the program that left the core file and the signal it went down on.&lt;BR /&gt;If you have toe source code and have compiled it with debugging info you can use gdb to debug the program.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Trond</description>
      <pubDate>Tue, 30 Apr 2002 05:40:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/view-core-dump/m-p/2713720#M721642</guid>
      <dc:creator>Trond Haugen</dc:creator>
      <dc:date>2002-04-30T05:40:16Z</dc:date>
    </item>
    <item>
      <title>Re: view core dump</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/view-core-dump/m-p/2713721#M721643</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Its simple to see the main reason that cause the core. Just use the cmd:&lt;BR /&gt;&lt;BR /&gt;what core&lt;BR /&gt;&lt;BR /&gt;"If you never try, never you??ll learn "</description>
      <pubDate>Thu, 02 May 2002 11:23:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/view-core-dump/m-p/2713721#M721643</guid>
      <dc:creator>Ricardo Bassoi</dc:creator>
      <dc:date>2002-05-02T11:23:51Z</dc:date>
    </item>
  </channel>
</rss>

