Using wdb "set thread-check" options on HP-PA

[Shweta_3]

Hello,

I have a multi-threaded applucation running on HP-PARISC (HP-UX B.11.23 U 9000/785)
The application is deadlocking, and initial investigation reveal a possibility of some threads exiting without releasing lock on mutex.

I saw that WDB provides for commands "set thread-check" to detect for threadlocks.
url: http://h21007.www2.hp.com/dspp/tech/tech_TechDocumentDetailPage_IDX/1,1701,6420,00.htmlhttp://h21007.www2.hp.com/dspp/tech/tech_TechDocumentDetailPage_IDX/1,1701,6420,00.html

I used "set thread-check on thread-exit-own-mutex on"
however my application exits with

Trace library -- Non-recoverable error.
Out of memory.
Exiting...

I don't see the gdb process really increase in size. Any pointers on how to use this option?
Any WDB specific forum?

$gdb --version
HP gdb 5.5.0 for PA-RISC 1.1 or 2.0 (narrow), HP-UX 11.00
and target hppa1.1-hp-hpux11.00.
Copyright 1986 - 2001 Free Software Foundation, Inc.
Hewlett-Packard Wildebeest 5.5.0 (based on GDB) is covered by the
GNU General Public License. Type "show copying" to see the conditions to
change it and/or distribute copies. Type "show warranty" for warranty/support.

[Dennis Handly]

>I don't see the gdb process really increase in size.

You need to look at the debuggee process. Saving this info in gdb would really slow things down.

>Any WDB specific forum?

It is lumped in with HP-UX devtools:
http://h21007.www2.hp.com/dspp/comm/comm_Community_Home_IDX/1,1273,,00.html

[Jini Susan George · Accepted solution]

Hello Shweta,

Could you please try with the command: "set thread-check thread-exit-own-mutex on" (that is without the 'on' after 'thread-check') and let us know if it helps ?

Regards,
Jini.

[Shweta_3]

Thank You Jini. This helped. Now the application is running in gdb. I hope to see some results.