<?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 analyzing core files using adb or wdb in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/analyzing-core-files-using-adb-or-wdb/m-p/3311422#M185658</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Can anybody tell me how to analyze core files in HP-UX using adb or wdb??/Step by step procedure will be highly appreciated.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Thanks and Regards,&lt;BR /&gt;&lt;BR /&gt;Amit Manna</description>
    <pubDate>Tue, 22 Jun 2004 00:35:31 GMT</pubDate>
    <dc:creator>Amit Manna_6</dc:creator>
    <dc:date>2004-06-22T00:35:31Z</dc:date>
    <item>
      <title>analyzing core files using adb or wdb</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/analyzing-core-files-using-adb-or-wdb/m-p/3311422#M185658</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Can anybody tell me how to analyze core files in HP-UX using adb or wdb??/Step by step procedure will be highly appreciated.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Thanks and Regards,&lt;BR /&gt;&lt;BR /&gt;Amit Manna</description>
      <pubDate>Tue, 22 Jun 2004 00:35:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/analyzing-core-files-using-adb-or-wdb/m-p/3311422#M185658</guid>
      <dc:creator>Amit Manna_6</dc:creator>
      <dc:date>2004-06-22T00:35:31Z</dc:date>
    </item>
    <item>
      <title>Re: analyzing core files using adb or wdb</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/analyzing-core-files-using-adb-or-wdb/m-p/3311423#M185659</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I have not done much of core analysis but at times stack trace helps.&lt;BR /&gt;&lt;BR /&gt;gdb core&lt;BR /&gt;bt&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;HTH&lt;BR /&gt;&lt;BR /&gt;manish</description>
      <pubDate>Tue, 22 Jun 2004 00:44:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/analyzing-core-files-using-adb-or-wdb/m-p/3311423#M185659</guid>
      <dc:creator>Manish Srivastava</dc:creator>
      <dc:date>2004-06-22T00:44:55Z</dc:date>
    </item>
    <item>
      <title>Re: analyzing core files using adb or wdb</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/analyzing-core-files-using-adb-or-wdb/m-p/3311424#M185660</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;For core dump analysis, you can use&lt;BR /&gt;file core &lt;BR /&gt;and&lt;BR /&gt;what core,&lt;BR /&gt;If you want detailed analysis use wdb:&lt;BR /&gt;&lt;BR /&gt;wdb program core&lt;BR /&gt;&lt;BR /&gt;where program is the executable that failed.&lt;BR /&gt;&lt;BR /&gt;You can download wdb from here:&lt;BR /&gt;&lt;A href="http://hp.com/go/wdb" target="_blank"&gt;http://hp.com/go/wdb&lt;/A&gt; &lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 22 Jun 2004 01:05:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/analyzing-core-files-using-adb-or-wdb/m-p/3311424#M185660</guid>
      <dc:creator>Shaikh Imran</dc:creator>
      <dc:date>2004-06-22T01:05:42Z</dc:date>
    </item>
    <item>
      <title>Re: analyzing core files using adb or wdb</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/analyzing-core-files-using-adb-or-wdb/m-p/3311425#M185661</link>
      <description>hi,&lt;BR /&gt;&lt;BR /&gt;using the file command will identify what application generated the core:&lt;BR /&gt;&lt;BR /&gt;# file core&lt;BR /&gt;&lt;BR /&gt;another basic guide to analyze core files is found in this HP doc:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&amp;amp;docId=200000063236268" target="_blank"&gt;http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&amp;amp;docId=200000063236268&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;regards.</description>
      <pubDate>Tue, 22 Jun 2004 01:22:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/analyzing-core-files-using-adb-or-wdb/m-p/3311425#M185661</guid>
      <dc:creator>Joseph Loo</dc:creator>
      <dc:date>2004-06-22T01:22:07Z</dc:date>
    </item>
    <item>
      <title>Re: analyzing core files using adb or wdb</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/analyzing-core-files-using-adb-or-wdb/m-p/3311426#M185662</link>
      <description>hai amit,&lt;BR /&gt;&lt;BR /&gt; Let's see about wdb core debugging,&lt;BR /&gt;&lt;BR /&gt;  Before debugging set the core size as&lt;BR /&gt;  # get the core size using&lt;BR /&gt;   ulimit -a (or) ulimit -c (or) ulimit&lt;BR /&gt;  # set your limit&lt;BR /&gt;   ulimit -c &lt;LIMIT-BYTES&gt; &lt;BR /&gt;   unlimited to make the usage as unlimited&lt;BR /&gt; &lt;BR /&gt;  gdb &lt;APPLIACTION-NAME which="" made="" core=""&gt; core-file&lt;BR /&gt;  gdb&amp;gt; bt&lt;BR /&gt;  &lt;BR /&gt;  it will show the cause for that core,&lt;BR /&gt;  &lt;BR /&gt;  gdb&amp;gt; info signals &lt;BR /&gt;  it will give the signal which effect the appliacation&lt;BR /&gt; &lt;BR /&gt;  gdb&amp;gt; where&lt;BR /&gt;  it can also used to detect the location of core dumped.&lt;BR /&gt;&lt;BR /&gt;  Good guide here at&lt;BR /&gt;  &lt;A href="http://devrsrc1.external.hp.com/devresource/Tools/wdb/doc/guide/index.html" target="_blank"&gt;http://devrsrc1.external.hp.com/devresource/Tools/wdb/doc/guide/index.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Muthukumar.&lt;/APPLIACTION-NAME&gt;&lt;/LIMIT-BYTES&gt;</description>
      <pubDate>Tue, 22 Jun 2004 01:28:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/analyzing-core-files-using-adb-or-wdb/m-p/3311426#M185662</guid>
      <dc:creator>Muthukumar_5</dc:creator>
      <dc:date>2004-06-22T01:28:02Z</dc:date>
    </item>
    <item>
      <title>Re: analyzing core files using adb or wdb</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/analyzing-core-files-using-adb-or-wdb/m-p/3311427#M185663</link>
      <description>hai,&lt;BR /&gt;&lt;BR /&gt; You can use the absolute debugger (adb) is the analysis of core files.&lt;BR /&gt;&lt;BR /&gt; adb &lt;APPLICATION with="" full="" pathname=""&gt; &lt;CORE with="" full="" path="" name=""&gt;&lt;BR /&gt;&lt;BR /&gt; adb&amp;gt; c&lt;BR /&gt; It will give the back trace&lt;BR /&gt; &lt;BR /&gt; adb&amp;gt; m&lt;BR /&gt; It will give the file mappings&lt;BR /&gt;&lt;BR /&gt; To know more about core file use&lt;BR /&gt;  core(4) man page and sys/core.h &lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Muthukumar &lt;BR /&gt;&lt;/CORE&gt;&lt;/APPLICATION&gt;</description>
      <pubDate>Tue, 22 Jun 2004 03:21:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/analyzing-core-files-using-adb-or-wdb/m-p/3311427#M185663</guid>
      <dc:creator>Muthukumar_5</dc:creator>
      <dc:date>2004-06-22T03:21:19Z</dc:date>
    </item>
    <item>
      <title>Re: analyzing core files using adb or wdb</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/analyzing-core-files-using-adb-or-wdb/m-p/3311428#M185664</link>
      <description>Hi Amit,&lt;BR /&gt;&lt;BR /&gt;Check out these threads:&lt;BR /&gt;&lt;BR /&gt;a) &lt;A href="http://forums1.itrc.hp.com/service/forums/bizsupport/questionanswer.do?threadId=20440" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/bizsupport/questionanswer.do?threadId=20440&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;b) &lt;A href="http://forums1.itrc.hp.com/service/forums/bizsupport/questionanswer.do?threadId=86495" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/bizsupport/questionanswer.do?threadId=86495&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;c) &lt;A href="http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=40484" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=40484&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;HTH.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Sri Ram&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 22 Jun 2004 08:03:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/analyzing-core-files-using-adb-or-wdb/m-p/3311428#M185664</guid>
      <dc:creator>R. Sri Ram Kishore_1</dc:creator>
      <dc:date>2004-06-22T08:03:21Z</dc:date>
    </item>
    <item>
      <title>Re: analyzing core files using adb or wdb</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/analyzing-core-files-using-adb-or-wdb/m-p/3311429#M185665</link>
      <description>Requirements for core accurate core analysis:&lt;BR /&gt;&lt;BR /&gt;1. complete, untruncated core file from binary&lt;BR /&gt;2. *exact* binary that caused core&lt;BR /&gt;3. *all* the shared libraries that match *exactly* at the time of the failure.   You can collect them and put them in a directory and set the environment variable GDB_SHLIB_PATH to point to this directory prior to running GDB&lt;BR /&gt;&lt;BR /&gt;It is often easiest to do an initial core analysis on the same machine where failure occurred. &lt;BR /&gt;&lt;BR /&gt;Can use chatr or ldd to find out complete list of shared libs.   gdb has info shared which will give you a list of shared libs loaded at time of failure.</description>
      <pubDate>Wed, 23 Jun 2004 07:13:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/analyzing-core-files-using-adb-or-wdb/m-p/3311429#M185665</guid>
      <dc:creator>Rick Beldin</dc:creator>
      <dc:date>2004-06-23T07:13:34Z</dc:date>
    </item>
  </channel>
</rss>

