Hi Abou Al Montacir There some other tests you can run just comment appropriate ones out and run again. During Segmentation fault the program gets core dumped and won't continue.
If you have an older kernel it is possible that uninitialized condition variables or mutices can cause it. How ever, stack corruption could be that cause for that, too. Bests, Joël On Thu, Sep 15, 2016 at 4:50 PM, Abou Al Montacir <abou.almonta...@sfr.fr> wrote: > Hi Joël, > > On Wed, 2016-09-14 at 15:38 +0200, Joël Krähemann wrote: > > Hi > > reproducing the critical parts in a unit test would be helpful > > Something like in the attachment. > > install dependencies: > > apt-get install libcunit1-dev > > Compile with > > gcc -g -o mutex_fail_test mutex_fail_test.c `pkg-config --cflags --libs > cunit` -pthread > > launch > > ./mutex_fail_test > > Thanks for that, > > Here are the results: > > $gcc -g -o mutex_fail_test mutex_fail_test.c `pkg-config --cflags --libs > cunit` -pthread > > $./mutex_fail_test > > > CUnit - A unit testing framework for C - Version 2.1-3 > http://cunit.sourceforge.net/ > > > Suite: MutexFailTest > Test: test of pthread_mutex_lock concurrently with unassigned pointer > ...Segmentation fault > > > -- > > Cheers, Abou Al Montacir > > >
