Thank you Eric and Stefaan. I'll try the tips you suggested.





On Fri, 1 Sep 2006 09:21:54 +0200, Stefaan A Eeckels <hoendech@ecc.lu>
wrote:

>On Thu, 31 Aug 2006 23:47:16 -0400
>Forte Agent <robertch@newscat.com> wrote:
>
>> I understand that we can analyze core file of processes that died, but
>> what about processes that hangs forever, consuming CPU? Is there any
>> particular approach we can take to analyze the hanging process? We
>> don't own source code of this process executable, so we cannot try
>> generating trace file.
>
>You can use tusc to trace the process while it runs. You can download
>the tusc shar file from:
>
><http://h21007.www2.hp.com/dspp/tech/tech_TechDocumentDetailPage_IDX/1,1701,2894,00.html>
>
>I doubt your program has been compiled with symbols, but the WDB
>debugger (a HP supported version of the GNU debugger GDB) can be
>attached to a running program. Check HP's WDB page at
><http://www.hp.com/go/wdb/>.
>
>Take care,
>
>--
>Stefaan A Eeckels