<?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: useracc failed in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/useracc-failed/m-p/4465976#M360484</link>
    <description>On the WDB page you can find this document:&lt;BR /&gt;Debugging core files using HP WDB&lt;BR /&gt;&lt;A href="http://www.hp.com/go/wdb" target="_blank"&gt;http://www.hp.com/go/wdb&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Basically on the same system that caused the core dump:&lt;BR /&gt;$ file core&lt;BR /&gt;(Gives you the signal and up to 14 bytes of the basename of the executable.&lt;BR /&gt;&lt;BR /&gt;$ gdb path-to/executable core&lt;BR /&gt;(gdb) bt&lt;BR /&gt;(gdb) q&lt;BR /&gt;&lt;BR /&gt;If it is a main thread, you should see main at the bottom.  If it is a thread, you should see some pthread on the bottom.&lt;BR /&gt;&lt;BR /&gt;By taking the difference in the $sp register from the top and bottom frames, you can compute your current stack size.</description>
    <pubDate>Fri, 24 Jul 2009 09:35:01 GMT</pubDate>
    <dc:creator>Dennis Handly</dc:creator>
    <dc:date>2009-07-24T09:35:01Z</dc:date>
    <item>
      <title>useracc failed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/useracc-failed/m-p/4465973#M360481</link>
      <description>Hi,&lt;BR /&gt;When i try to bring up WAS in HP-UX and do heavy transactions,core dump is getting formed with following error&lt;BR /&gt;&lt;BR /&gt;sendsig: useracc failed. 0x9fffffffb977be00 0x00000000005000&lt;BR /&gt;&lt;BR /&gt;Pid 25126 was killed due to failure in writing the signal context - possible stack overflow.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Kindly assist</description>
      <pubDate>Fri, 24 Jul 2009 02:19:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/useracc-failed/m-p/4465973#M360481</guid>
      <dc:creator>nish_1</dc:creator>
      <dc:date>2009-07-24T02:19:46Z</dc:date>
    </item>
    <item>
      <title>Re: useracc failed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/useracc-failed/m-p/4465974#M360482</link>
      <description>As it said, you either have a main stack or a thread stack overflow.&lt;BR /&gt;You need to get a stack trace (use gdb) to determine which.</description>
      <pubDate>Fri, 24 Jul 2009 08:45:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/useracc-failed/m-p/4465974#M360482</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2009-07-24T08:45:00Z</dc:date>
    </item>
    <item>
      <title>Re: useracc failed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/useracc-failed/m-p/4465975#M360483</link>
      <description>This is the first time I am told to analyse core dump..I dont know much about this..can u pls elaborate on it</description>
      <pubDate>Fri, 24 Jul 2009 09:01:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/useracc-failed/m-p/4465975#M360483</guid>
      <dc:creator>nish_1</dc:creator>
      <dc:date>2009-07-24T09:01:21Z</dc:date>
    </item>
    <item>
      <title>Re: useracc failed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/useracc-failed/m-p/4465976#M360484</link>
      <description>On the WDB page you can find this document:&lt;BR /&gt;Debugging core files using HP WDB&lt;BR /&gt;&lt;A href="http://www.hp.com/go/wdb" target="_blank"&gt;http://www.hp.com/go/wdb&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Basically on the same system that caused the core dump:&lt;BR /&gt;$ file core&lt;BR /&gt;(Gives you the signal and up to 14 bytes of the basename of the executable.&lt;BR /&gt;&lt;BR /&gt;$ gdb path-to/executable core&lt;BR /&gt;(gdb) bt&lt;BR /&gt;(gdb) q&lt;BR /&gt;&lt;BR /&gt;If it is a main thread, you should see main at the bottom.  If it is a thread, you should see some pthread on the bottom.&lt;BR /&gt;&lt;BR /&gt;By taking the difference in the $sp register from the top and bottom frames, you can compute your current stack size.</description>
      <pubDate>Fri, 24 Jul 2009 09:35:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/useracc-failed/m-p/4465976#M360484</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2009-07-24T09:35:01Z</dc:date>
    </item>
  </channel>
</rss>

