<?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: Are there any debug tools which can detect program's hang-up location? in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/are-there-any-debug-tools-which-can-detect-program-s-hang-up/m-p/2966021#M720337</link>
    <description>&lt;BR /&gt;&lt;BR /&gt;Hi,&lt;BR /&gt;&lt;BR /&gt;One thing  you could try is the following:&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;  . when the program seems to hang,  send&lt;BR /&gt;    a  sigabrt  to the process  &lt;BR /&gt;    ( kill -6  PID )&lt;BR /&gt;    this will produce a core file.&lt;BR /&gt;&lt;BR /&gt;  . Use a debugger to get the call-stack.&lt;BR /&gt;    With gdb  this can be done as follows:&lt;BR /&gt;&lt;BR /&gt;      gdb -tui  &lt;EXECUTABLE&gt;  core&lt;BR /&gt;      (gdb)  info  stack&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Another thing you could try  is to use&lt;BR /&gt;the debugger to attach to the running process.&lt;BR /&gt;&lt;BR /&gt;Regards &lt;BR /&gt;Olav&lt;BR /&gt;&lt;BR /&gt;&lt;/EXECUTABLE&gt;</description>
    <pubDate>Mon, 05 May 2003 18:38:02 GMT</pubDate>
    <dc:creator>Olav Baadsvik</dc:creator>
    <dc:date>2003-05-05T18:38:02Z</dc:date>
    <item>
      <title>Are there any debug tools which can detect program's hang-up location?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/are-there-any-debug-tools-which-can-detect-program-s-hang-up/m-p/2966019#M720335</link>
      <description>I am debugging a daemon C++ program which is locked up randomly for some reason. Are&lt;BR /&gt;there any tools which can trace the process and detect the hang-up location.  (such as which&lt;BR /&gt; C++ statement or function the program is locked up?). &lt;BR /&gt;&lt;BR /&gt;OS: hp-ux 10.20. Language C++&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;&lt;BR /&gt;Liping</description>
      <pubDate>Mon, 05 May 2003 17:18:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/are-there-any-debug-tools-which-can-detect-program-s-hang-up/m-p/2966019#M720335</guid>
      <dc:creator>liping guo</dc:creator>
      <dc:date>2003-05-05T17:18:08Z</dc:date>
    </item>
    <item>
      <title>Re: Are there any debug tools which can detect program's hang-up location?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/are-there-any-debug-tools-which-can-detect-program-s-hang-up/m-p/2966020#M720336</link>
      <description>I guess that will be "tusc"&lt;BR /&gt;&lt;BR /&gt;Go to following site and search for tusc&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://hpux.cs.utah.edu/" target="_blank"&gt;http://hpux.cs.utah.edu/&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Sachin</description>
      <pubDate>Mon, 05 May 2003 17:21:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/are-there-any-debug-tools-which-can-detect-program-s-hang-up/m-p/2966020#M720336</guid>
      <dc:creator>Sachin Patel</dc:creator>
      <dc:date>2003-05-05T17:21:28Z</dc:date>
    </item>
    <item>
      <title>Re: Are there any debug tools which can detect program's hang-up location?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/are-there-any-debug-tools-which-can-detect-program-s-hang-up/m-p/2966021#M720337</link>
      <description>&lt;BR /&gt;&lt;BR /&gt;Hi,&lt;BR /&gt;&lt;BR /&gt;One thing  you could try is the following:&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;  . when the program seems to hang,  send&lt;BR /&gt;    a  sigabrt  to the process  &lt;BR /&gt;    ( kill -6  PID )&lt;BR /&gt;    this will produce a core file.&lt;BR /&gt;&lt;BR /&gt;  . Use a debugger to get the call-stack.&lt;BR /&gt;    With gdb  this can be done as follows:&lt;BR /&gt;&lt;BR /&gt;      gdb -tui  &lt;EXECUTABLE&gt;  core&lt;BR /&gt;      (gdb)  info  stack&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Another thing you could try  is to use&lt;BR /&gt;the debugger to attach to the running process.&lt;BR /&gt;&lt;BR /&gt;Regards &lt;BR /&gt;Olav&lt;BR /&gt;&lt;BR /&gt;&lt;/EXECUTABLE&gt;</description>
      <pubDate>Mon, 05 May 2003 18:38:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/are-there-any-debug-tools-which-can-detect-program-s-hang-up/m-p/2966021#M720337</guid>
      <dc:creator>Olav Baadsvik</dc:creator>
      <dc:date>2003-05-05T18:38:02Z</dc:date>
    </item>
    <item>
      <title>Re: Are there any debug tools which can detect program's hang-up location?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/are-there-any-debug-tools-which-can-detect-program-s-hang-up/m-p/2966022#M720338</link>
      <description>DDE will allow you to seize a running process, set break points, examine variable, single step, etc.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://docs.hp.com/cgi-bin/onlinedocs.py?mpn=B3476-90015&amp;amp;service=hpux&amp;amp;path=00/00/1&amp;amp;title=HP/DDE%20Debugger%20User%27s%20Guide" target="_blank"&gt;http://docs.hp.com/cgi-bin/onlinedocs.py?mpn=B3476-90015&amp;amp;service=hpux&amp;amp;path=00/00/1&amp;amp;title=HP/DDE%20Debugger%20User%27s%20Guide&lt;/A&gt;</description>
      <pubDate>Mon, 05 May 2003 19:15:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/are-there-any-debug-tools-which-can-detect-program-s-hang-up/m-p/2966022#M720338</guid>
      <dc:creator>Christopher Caldwell</dc:creator>
      <dc:date>2003-05-05T19:15:00Z</dc:date>
    </item>
    <item>
      <title>Re: Are there any debug tools which can detect program's hang-up location?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/are-there-any-debug-tools-which-can-detect-program-s-hang-up/m-p/2966023#M720339</link>
      <description>I am reading into this that you have the source code for this daemon. If so, my favorite technique (and one that I always do anyway) is to place assert()'s at the beginning and return(s) of each function. You pay no penalty if you complile with -NDEBUG and otherwise you have a log of each function writen to stderr.&lt;BR /&gt;&lt;BR /&gt;Again, this is my standard practice and has served me well over the years in quickly finding problems like yours.&lt;BR /&gt;</description>
      <pubDate>Mon, 05 May 2003 19:24:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/are-there-any-debug-tools-which-can-detect-program-s-hang-up/m-p/2966023#M720339</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2003-05-05T19:24:36Z</dc:date>
    </item>
    <item>
      <title>Re: Are there any debug tools which can detect program's hang-up location?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/are-there-any-debug-tools-which-can-detect-program-s-hang-up/m-p/2966024#M720340</link>
      <description>Hi, Dear friends,&lt;BR /&gt;Your information is really helpful. I am going to try them.&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;&lt;BR /&gt;Liping</description>
      <pubDate>Tue, 06 May 2003 12:30:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/are-there-any-debug-tools-which-can-detect-program-s-hang-up/m-p/2966024#M720340</guid>
      <dc:creator>liping guo</dc:creator>
      <dc:date>2003-05-06T12:30:55Z</dc:date>
    </item>
  </channel>
</rss>

