Date: Fri, 4 Sep 2015 12:05:18 -0400 From: Rich Felker <dalias@...c.org> To: musl@...ts.openwall.com Subject: Re: Using PTHREAD_MUTEX_RECURSIVE and PTHREAD_MUTEX_ERRORCHECK leads to segmentation fault On Fri, Sep 04, 2015 at 03:11:23PM +0300, Eugene wrote: > Unfortunately I can reproduce it only with real configuration. > I has tried to write small program to reproduce problem but without luck. > > I can add some debug or asserts if it helps. Logging mutex lock/unlock and destroy/free would show whether a locked mutex is destroyed or freed, I think. Another approach would be to add to pthread_mutex_destroy a check for whether the mutex is locked, and make it crash. This would only catch invalid destroy though, not free-without-destroy. Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.