Rajesh,

rajeshjangam@gmail.com wrote:
> It hangs after running for sometime (2-3 hours) in ksleep.

The process hangs here while trying to acquire a mutex. The very
likely reason for this is that this mutex is in a "locked" state
and the lock owner has already exited without doing the unlock.

Do you know if this process ever became multi-threaded before it
got hung? To get more insights, would you please do the following
after you attach thru' gdb and post the output:
(gdb) f 1
(gdb) x /40x $r26

While it does appear like some 'libc' mutex, it is hard to
tell which mutex is this without a proper stacktrace. It will
be very helpful, if you could come with a test case. If not,
we at least need a good stacktrace. Are you running the latest
version of 'gdb' from HP?

Thanks,
--Vasu