<?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: core dump reading in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/core-dump-reading/m-p/3880676#M280035</link>
    <description>Inesa,&lt;BR /&gt;&lt;BR /&gt;You might want to try with:&lt;BR /&gt;&lt;BR /&gt;strings core | grep -i fatal&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;Jaime.</description>
    <pubDate>Mon, 16 Oct 2006 06:56:28 GMT</pubDate>
    <dc:creator>Jaime Bolanos Rojas.</dc:creator>
    <dc:date>2006-10-16T06:56:28Z</dc:date>
    <item>
      <title>core dump reading</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/core-dump-reading/m-p/3880675#M280034</link>
      <description>Good Morning!&lt;BR /&gt;&lt;BR /&gt;Please help me to "read" core-dump file in order to find out the problem. I know that I could use "adb", but how? My system is PA-RISK 11.11.&lt;BR /&gt;Core dump is:"/root/core" from 15/10/2006.&lt;BR /&gt;</description>
      <pubDate>Mon, 16 Oct 2006 06:49:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/core-dump-reading/m-p/3880675#M280034</guid>
      <dc:creator>Inesa Clinko</dc:creator>
      <dc:date>2006-10-16T06:49:16Z</dc:date>
    </item>
    <item>
      <title>Re: core dump reading</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/core-dump-reading/m-p/3880676#M280035</link>
      <description>Inesa,&lt;BR /&gt;&lt;BR /&gt;You might want to try with:&lt;BR /&gt;&lt;BR /&gt;strings core | grep -i fatal&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;Jaime.</description>
      <pubDate>Mon, 16 Oct 2006 06:56:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/core-dump-reading/m-p/3880676#M280035</guid>
      <dc:creator>Jaime Bolanos Rojas.</dc:creator>
      <dc:date>2006-10-16T06:56:28Z</dc:date>
    </item>
    <item>
      <title>Re: core dump reading</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/core-dump-reading/m-p/3880677#M280036</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;to identify the program that created the core file, run the command&lt;BR /&gt;file /path/to/core&lt;BR /&gt;&lt;BR /&gt;If the program name is one of your self developped ones, load program and core in the debugger.&lt;BR /&gt;&lt;BR /&gt;mfG Peter</description>
      <pubDate>Mon, 16 Oct 2006 07:02:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/core-dump-reading/m-p/3880677#M280036</guid>
      <dc:creator>Peter Nikitka</dc:creator>
      <dc:date>2006-10-16T07:02:52Z</dc:date>
    </item>
    <item>
      <title>Re: core dump reading</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/core-dump-reading/m-p/3880678#M280037</link>
      <description>Hi Inesa,&lt;BR /&gt;&lt;BR /&gt;Sampel "gdb"&lt;BR /&gt;&lt;BR /&gt;# file /oracle/oraclesid/scripts/core&lt;BR /&gt;&lt;BR /&gt;ELF-64 core file - PA-RISC 2.0 from 'sqlplus' - received SIGQUIT&lt;BR /&gt;&lt;BR /&gt;# gdb /opt/oracle92/bin/sqlplus /home/oracle/oraclesid/scripts/core&lt;BR /&gt;&lt;BR /&gt;...&lt;BR /&gt;(gdb) bt&lt;BR /&gt;&lt;BR /&gt;#0  0xc0000000002fc3ec in adjtime+0x44 () from /usr/lib/pa20_64/libc.2&lt;BR /&gt;#1  0xc000000000307124 in wait3+0x94 () from /usr/lib/pa20_64/libc.2&lt;BR /&gt;Error accessing memory address 0x0: Invalid argument.&lt;BR /&gt;&lt;BR /&gt;(gdb) quit&lt;BR /&gt;&lt;BR /&gt;rgs&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 16 Oct 2006 07:21:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/core-dump-reading/m-p/3880678#M280037</guid>
      <dc:creator>rariasn</dc:creator>
      <dc:date>2006-10-16T07:21:43Z</dc:date>
    </item>
    <item>
      <title>Re: core dump reading</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/core-dump-reading/m-p/3880679#M280038</link>
      <description>Hi,&lt;BR /&gt;GDB is a useful tool for debugging core files generated by processes.&lt;BR /&gt;&lt;BR /&gt;To find out more information regarding GDB visit;&lt;BR /&gt;&lt;A href="http://www.gnu.org/software/gdb/documentation/" target="_blank"&gt;http://www.gnu.org/software/gdb/documentation/&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Running GDB&lt;BR /&gt;&lt;BR /&gt;[a]. Determine the location of GDB, whereis gdb&lt;BR /&gt;[b].  Execute gdb from the directory returned by the whereis command. Note the arguments to gdb are&lt;BR /&gt;          Process&lt;BR /&gt;         Core file location&lt;BR /&gt;[c]. Example, to analysis the core file core.225 located in the /home/mcadmin/CORE-FILES/applications    directory which was generated by the mobi process run gdb as follows&lt;BR /&gt;&lt;BR /&gt;gdb /apps/picasso/bin/mobi /home/mcadmin/CORE-FILES/applications/core.225&lt;BR /&gt;&lt;BR /&gt;[a].    To gather backtrace useful to analysis the problem type bt&lt;BR /&gt;[b].  Save this backtrace to a file&lt;BR /&gt;[c]. To quit gdb, type quit</description>
      <pubDate>Mon, 16 Oct 2006 07:30:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/core-dump-reading/m-p/3880679#M280038</guid>
      <dc:creator>Senthil Prabu.S_1</dc:creator>
      <dc:date>2006-10-16T07:30:06Z</dc:date>
    </item>
  </channel>
</rss>

