https://bugs.kde.org/show_bug.cgi?id=392331
--- Comment #5 from Paul Floyd <pjfl...@wanadoo.fr> --- This message is generated from static void evh__HG_PTHREAD_COND_SIGNAL_PRE ( ThreadId tid, void* cond ) Which looks like the wrapper function called before a pthread_cond_signal And there is the comment // Hmm. POSIX doesn't actually say that it's an error to call // pthread_cond_signal with the associated mutex being unlocked. // Although it does say that it should be "if consistent scheduling // is desired." For that reason, print "dubious" if the lock isn't // held by any thread. Skip the "dubious" if it is held by some // other thread; that sounds straight-out wrong. And the corresponding doc. https://pubs.opengroup.org/onlinepubs/9699919799/ I'm not sure that we want to change this. I see two other possibilities - user suppression - add a command line option, something like --check_cond_signal_mutex -- You are receiving this mail because: You are watching all bug changes.
