{"push_id":982667228,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"4f3a996561445ba82c854bb2b674f975f596e884","before":"09092b6535b711b9b734ed0c047c671de9e6cafd","commits":[{"sha":"4f3a996561445ba82c854bb2b674f975f596e884","author":{"email":"c8ebd57a6866419c878c96a72702791f0ba50219@redhat.com","name":"Lukas Slebodnik"},"message":"sss_idmap-tests: Fix segmentation fault\n\nI can reproduce it only with clang.\nBut it's tipical off by one error.\n\nsh$ ./sss_idmap-tests\nRunning suite(s): IDMAP\nSegmentation fault (core dumped)\n\nRunning suite(s): IDMAP\n==2644== Process terminating with default action of signal 11 (SIGSEGV)\n==2644==  Access not within mapped region at address 0xA08F430\n==2644==    at 0x4C2CC53: strcmp (vg_replace_strmem.c:842)\n==2644==    by 0x4060DA: idmap_test_sid2uid_additional_secondary_slices (sss_idmap-tests.c:451)\n==2644==    by 0x503C78A: ??? (in /usr/lib64/libcheck.so.0.0.0)\n==2644==    by 0x503CB7C: srunner_run (in /usr/lib64/libcheck.so.0.0.0)\n==2644==    by 0x4061EE: main (sss_idmap-tests.c:965)\n==2644==  If you believe this happened as a result of a stack\n==2644==  overflow in your program's main thread (unlikely but\n==2644==  possible), you can try to increase the size of the\n==2644==  main thread stack using the --main-stacksize= flag.\n==2644==  The main thread stack size used in this run was 8388608.\n\nReviewed-by: Sumit Bose <sbose@redhat.com>","distinct":true,"url":"https://api.github.com/repos/SSSD/sssd/commits/4f3a996561445ba82c854bb2b674f975f596e884"}]}