FWIW, you can create PTHREAD_MUTEX_ERRORCHECK_NP mutexes (see the man
pages for pthread_mutexattr_init and pthread_mutex_init) to have the
'thread trying to lock the same mutex twice' case detected.
This will help find 'duh' errors in one thread, not solve real deadlocks
(for those, I find it's a
MY CODE.
-Original Message-
From: Don Dade [mailto:[EMAIL PROTECTED]
Sent: Friday, March 07, 2003 12:20 AM
To: [EMAIL PROTECTED]
Subject: Re: pthread_mutex_lock call hangs
Hi Ajay,
This is the normal sequence for LinuxThreads pthread_mutex_lock(). I
would
guess that you've got a
nsal
> Sent: Friday, March 07, 2003 3:11 PM
> To: [EMAIL PROTECTED]
> Subject: RE: pthread_mutex_lock call hangs
>
>
> But IS THAT POSSIBLE?? I mean that release mode binaries do not report a
> deadlock??
>
> Only difference between two build is of "-g" flag. T
Answers pleaaase
-Original Message-
From: Ajay Bansal
Sent: Friday, March 07, 2003 3:11 PM
To: [EMAIL PROTECTED]
Subject: RE: pthread_mutex_lock call hangs
But IS THAT POSSIBLE?? I mean that release mode binaries do not report a
deadlock??
Only difference between two build is
EMAIL PROTECTED]
Sent: Friday, March 07, 2003 12:20 AM
To: [EMAIL PROTECTED]
Subject: Re: pthread_mutex_lock call hangs
Hi Ajay,
This is the normal sequence for LinuxThreads pthread_mutex_lock(). I
would
guess that you've got a very subtle bug that is causing a deadlock when
you
compile an
Hi Ajay,
This is the normal sequence for LinuxThreads pthread_mutex_lock(). I would
guess that you've got a very subtle bug that is causing a deadlock when you
compile and run with debugging turned on.
I'd go through the code and find all the possible ways in which you could
have nested mute
