Laravel.io 
==2759== Helgrind, a thread error detector
==2759== Copyright (C) 2007-2017, and GNU GPL'd, by OpenWorks LLP et al.
==2759== Using Valgrind-3.22.0 and LibVEX; rerun with -h for copyright info
==2759== Command: ./logsd
==2759== 
==2759== ---Thread-Announcement------------------------------------------
==2759== 
==2759== Thread #1 is the program's root thread
==2759== 
==2759== ---Thread-Announcement------------------------------------------
==2759== 
==2759== Thread #2 was created
==2759==    at 0x4A92BD3: clone (clone.S:76)
==2759==    by 0x4A92CE0: __clone_internal_fallback (clone-internal.c:64)
==2759==    by 0x4A92CE0: __clone_internal (clone-internal.c:109)
==2759==    by 0x4A05F4F: create_thread (pthread_create.c:297)
==2759==    by 0x4A06AAF: pthread_create@@GLIBC_2.34 (pthread_create.c:836)
==2759==    by 0x48566F5: ??? (in /usr/lib64/valgrind/valgrind/vgpreload_helgrind-amd64-linux.so)
==2759==    by 0x10B497: createThread__proceduresZtcp83erver_u45 (in /home/lenz/LogSearch/logsd)
==2759==    by 0x1146A9: startServer__proceduresZtcp83erver_u11 (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114B4B: NimMainModule (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114AB5: NimMainInner (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114AC6: NimMain (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114B00: main (in /home/lenz/LogSearch/logsd)
==2759== 
==2759== ----------------------------------------------------------------
==2759== 
==2759==  Lock at 0x11A360 was first observed
==2759==    at 0x4858067: pthread_mutex_init (in /usr/lib64/valgrind/valgrind/vgpreload_helgrind-amd64-linux.so)
==2759==    by 0x11387C: initLock__coreZlocks_u7 (in /home/lenz/LogSearch/logsd)
==2759==    by 0x1149A1: atmproceduresatstcpServerdotnim_Init000 (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114A98: PreMainInner (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114AA9: PreMain (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114AC1: NimMain (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114B00: main (in /home/lenz/LogSearch/logsd)
==2759==  Address 0x11a360 is 0 bytes inside data symbol "lock__proceduresZtcp83erver_u5"
==2759== 
==2759== Possible data race during read of size 8 at 0x1FFEFFF5B0 by thread #1
==2759== Locks held: 1, at address 0x11A360
==2759==    at 0x113977: running__proceduresZtcp83erver_u31 (in /home/lenz/LogSearch/logsd)
==2759==    by 0x11437E: startServer__proceduresZtcp83erver_u11 (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114B4B: NimMainModule (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114AB5: NimMainInner (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114AC6: NimMain (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114B00: main (in /home/lenz/LogSearch/logsd)
==2759== 
==2759== This conflicts with a previous write of size 8 by thread #2
==2759== Locks held: none
==2759==    at 0x10B335: threadProcWrapper__proceduresZtcp83erver_u66 (in /home/lenz/LogSearch/logsd)
==2759==    by 0x48568F6: ??? (in /usr/lib64/valgrind/valgrind/vgpreload_helgrind-amd64-linux.so)
==2759==    by 0x4A0645A: start_thread (pthread_create.c:447)
==2759==    by 0x4A92BE3: clone (clone.S:100)
==2759==  Address 0x1ffefff5b0 is on thread #1's stack
==2759==  in frame #1, created by startServer__proceduresZtcp83erver_u11 (???:)
==2759== 
==2759== ----------------------------------------------------------------
==2759== 
==2759==  Lock at 0x11A360 was first observed
==2759==    at 0x4858067: pthread_mutex_init (in /usr/lib64/valgrind/valgrind/vgpreload_helgrind-amd64-linux.so)
==2759==    by 0x11387C: initLock__coreZlocks_u7 (in /home/lenz/LogSearch/logsd)
==2759==    by 0x1149A1: atmproceduresatstcpServerdotnim_Init000 (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114A98: PreMainInner (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114AA9: PreMain (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114AC1: NimMain (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114B00: main (in /home/lenz/LogSearch/logsd)
==2759==  Address 0x11a360 is 0 bytes inside data symbol "lock__proceduresZtcp83erver_u5"
==2759== 
==2759== Possible data race during write of size 8 at 0x1FFEFFF5A0 by thread #1
==2759== Locks held: 1, at address 0x11A360
==2759==    at 0x10B3B2: createThread__proceduresZtcp83erver_u45 (in /home/lenz/LogSearch/logsd)
==2759==    by 0x1146A9: startServer__proceduresZtcp83erver_u11 (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114B4B: NimMainModule (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114AB5: NimMainInner (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114AC6: NimMain (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114B00: main (in /home/lenz/LogSearch/logsd)
==2759== 
==2759== This conflicts with a previous write of size 8 by thread #2
==2759== Locks held: none
==2759==    at 0x10B32A: threadProcWrapper__proceduresZtcp83erver_u66 (in /home/lenz/LogSearch/logsd)
==2759==    by 0x48568F6: ??? (in /usr/lib64/valgrind/valgrind/vgpreload_helgrind-amd64-linux.so)
==2759==    by 0x4A0645A: start_thread (pthread_create.c:447)
==2759==    by 0x4A92BE3: clone (clone.S:100)
==2759==  Address 0x1ffefff5a0 is on thread #1's stack
==2759==  in frame #1, created by startServer__proceduresZtcp83erver_u11 (???:)
==2759== 
==2759== ----------------------------------------------------------------
==2759== 
==2759==  Lock at 0x11A360 was first observed
==2759==    at 0x4858067: pthread_mutex_init (in /usr/lib64/valgrind/valgrind/vgpreload_helgrind-amd64-linux.so)
==2759==    by 0x11387C: initLock__coreZlocks_u7 (in /home/lenz/LogSearch/logsd)
==2759==    by 0x1149A1: atmproceduresatstcpServerdotnim_Init000 (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114A98: PreMainInner (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114AA9: PreMain (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114AC1: NimMain (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114B00: main (in /home/lenz/LogSearch/logsd)
==2759==  Address 0x11a360 is 0 bytes inside data symbol "lock__proceduresZtcp83erver_u5"
==2759== 
==2759== Possible data race during write of size 8 at 0x1FFEFFF5B0 by thread #1
==2759== Locks held: 1, at address 0x11A360
==2759==    at 0x10B3D7: createThread__proceduresZtcp83erver_u45 (in /home/lenz/LogSearch/logsd)
==2759==    by 0x1146A9: startServer__proceduresZtcp83erver_u11 (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114B4B: NimMainModule (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114AB5: NimMainInner (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114AC6: NimMain (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114B00: main (in /home/lenz/LogSearch/logsd)
==2759== 
==2759== This conflicts with a previous write of size 8 by thread #2
==2759== Locks held: none
==2759==    at 0x10B335: threadProcWrapper__proceduresZtcp83erver_u66 (in /home/lenz/LogSearch/logsd)
==2759==    by 0x48568F6: ??? (in /usr/lib64/valgrind/valgrind/vgpreload_helgrind-amd64-linux.so)
==2759==    by 0x4A0645A: start_thread (pthread_create.c:447)
==2759==    by 0x4A92BE3: clone (clone.S:100)
==2759==  Address 0x1ffefff5b0 is on thread #1's stack
==2759==  in frame #1, created by startServer__proceduresZtcp83erver_u11 (???:)
==2759== 
==2759== ---Thread-Announcement------------------------------------------
==2759== 
==2759== Thread #12 was created
==2759==    at 0x4A92BD3: clone (clone.S:76)
==2759==    by 0x4A92CE0: __clone_internal_fallback (clone-internal.c:64)
==2759==    by 0x4A92CE0: __clone_internal (clone-internal.c:109)
==2759==    by 0x4A05F4F: create_thread (pthread_create.c:297)
==2759==    by 0x4A06AAF: pthread_create@@GLIBC_2.34 (pthread_create.c:836)
==2759==    by 0x48566F5: ??? (in /usr/lib64/valgrind/valgrind/vgpreload_helgrind-amd64-linux.so)
==2759==    by 0x10B497: createThread__proceduresZtcp83erver_u45 (in /home/lenz/LogSearch/logsd)
==2759==    by 0x1146A9: startServer__proceduresZtcp83erver_u11 (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114B4B: NimMainModule (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114AB5: NimMainInner (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114AC6: NimMain (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114B00: main (in /home/lenz/LogSearch/logsd)
==2759== 
==2759== ----------------------------------------------------------------
==2759== 
==2759==  Lock at 0x11A360 was first observed
==2759==    at 0x4858067: pthread_mutex_init (in /usr/lib64/valgrind/valgrind/vgpreload_helgrind-amd64-linux.so)
==2759==    by 0x11387C: initLock__coreZlocks_u7 (in /home/lenz/LogSearch/logsd)
==2759==    by 0x1149A1: atmproceduresatstcpServerdotnim_Init000 (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114A98: PreMainInner (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114AA9: PreMain (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114AC1: NimMain (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114B00: main (in /home/lenz/LogSearch/logsd)
==2759==  Address 0x11a360 is 0 bytes inside data symbol "lock__proceduresZtcp83erver_u5"
==2759== 
==2759== Possible data race during read of size 8 at 0x1FFEFFF5A0 by thread #12
==2759== Locks held: none
==2759==    at 0x10B313: threadProcWrapper__proceduresZtcp83erver_u66 (in /home/lenz/LogSearch/logsd)
==2759==    by 0x48568F6: ??? (in /usr/lib64/valgrind/valgrind/vgpreload_helgrind-amd64-linux.so)
==2759==    by 0x4A0645A: start_thread (pthread_create.c:447)
==2759==    by 0x4A92BE3: clone (clone.S:100)
==2759== 
==2759== This conflicts with a previous write of size 8 by thread #1
==2759== Locks held: 1, at address 0x11A360
==2759==    at 0x10B3B2: createThread__proceduresZtcp83erver_u45 (in /home/lenz/LogSearch/logsd)
==2759==    by 0x1146A9: startServer__proceduresZtcp83erver_u11 (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114B4B: NimMainModule (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114AB5: NimMainInner (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114AC6: NimMain (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114B00: main (in /home/lenz/LogSearch/logsd)
==2759==  Address 0x1ffefff5a0 is on thread #1's stack
==2759==  in frame #6, created by startServer__proceduresZtcp83erver_u11 (???:)
==2759== 
==2759== ----------------------------------------------------------------
==2759== 
==2759==  Lock at 0x11A360 was first observed
==2759==    at 0x4858067: pthread_mutex_init (in /usr/lib64/valgrind/valgrind/vgpreload_helgrind-amd64-linux.so)
==2759==    by 0x11387C: initLock__coreZlocks_u7 (in /home/lenz/LogSearch/logsd)
==2759==    by 0x1149A1: atmproceduresatstcpServerdotnim_Init000 (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114A98: PreMainInner (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114AA9: PreMain (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114AC1: NimMain (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114B00: main (in /home/lenz/LogSearch/logsd)
==2759==  Address 0x11a360 is 0 bytes inside data symbol "lock__proceduresZtcp83erver_u5"
==2759== 
==2759== Possible data race during read of size 8 at 0x1FFEFFF5B0 by thread #12
==2759== Locks held: none
==2759==    at 0x10F481: threadProcWrapDispatch__proceduresZtcp83erver_u88 (in /home/lenz/LogSearch/logsd)
==2759==    by 0x10F5E1: threadProcWrapStackFrame__proceduresZtcp83erver_u79 (in /home/lenz/LogSearch/logsd)
==2759==    by 0x10B325: threadProcWrapper__proceduresZtcp83erver_u66 (in /home/lenz/LogSearch/logsd)
==2759==    by 0x48568F6: ??? (in /usr/lib64/valgrind/valgrind/vgpreload_helgrind-amd64-linux.so)
==2759==    by 0x4A0645A: start_thread (pthread_create.c:447)
==2759==    by 0x4A92BE3: clone (clone.S:100)
==2759== 
==2759== This conflicts with a previous write of size 8 by thread #1
==2759== Locks held: 1, at address 0x11A360
==2759==    at 0x10B3D7: createThread__proceduresZtcp83erver_u45 (in /home/lenz/LogSearch/logsd)
==2759==    by 0x1146A9: startServer__proceduresZtcp83erver_u11 (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114B4B: NimMainModule (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114AB5: NimMainInner (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114AC6: NimMain (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114B00: main (in /home/lenz/LogSearch/logsd)
==2759==  Address 0x1ffefff5b0 is on thread #1's stack
==2759==  in frame #6, created by startServer__proceduresZtcp83erver_u11 (???:)
==2759== 
==2759== ----------------------------------------------------------------
==2759== 
==2759==  Lock at 0x11A360 was first observed
==2759==    at 0x4858067: pthread_mutex_init (in /usr/lib64/valgrind/valgrind/vgpreload_helgrind-amd64-linux.so)
==2759==    by 0x11387C: initLock__coreZlocks_u7 (in /home/lenz/LogSearch/logsd)
==2759==    by 0x1149A1: atmproceduresatstcpServerdotnim_Init000 (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114A98: PreMainInner (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114AA9: PreMain (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114AC1: NimMain (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114B00: main (in /home/lenz/LogSearch/logsd)
==2759==  Address 0x11a360 is 0 bytes inside data symbol "lock__proceduresZtcp83erver_u5"
==2759== 
==2759== Possible data race during write of size 8 at 0x1FFEFFF5A0 by thread #12
==2759== Locks held: none
==2759==    at 0x10B32A: threadProcWrapper__proceduresZtcp83erver_u66 (in /home/lenz/LogSearch/logsd)
==2759==    by 0x48568F6: ??? (in /usr/lib64/valgrind/valgrind/vgpreload_helgrind-amd64-linux.so)
==2759==    by 0x4A0645A: start_thread (pthread_create.c:447)
==2759==    by 0x4A92BE3: clone (clone.S:100)
==2759== 
==2759== This conflicts with a previous write of size 8 by thread #1
==2759== Locks held: 1, at address 0x11A360
==2759==    at 0x10B3B2: createThread__proceduresZtcp83erver_u45 (in /home/lenz/LogSearch/logsd)
==2759==    by 0x1146A9: startServer__proceduresZtcp83erver_u11 (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114B4B: NimMainModule (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114AB5: NimMainInner (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114AC6: NimMain (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114B00: main (in /home/lenz/LogSearch/logsd)
==2759==  Address 0x1ffefff5a0 is on thread #1's stack
==2759==  in frame #3, created by startServer__proceduresZtcp83erver_u11 (???:)
==2759== 
==2759== ----------------------------------------------------------------
==2759== 
==2759==  Lock at 0x11A360 was first observed
==2759==    at 0x4858067: pthread_mutex_init (in /usr/lib64/valgrind/valgrind/vgpreload_helgrind-amd64-linux.so)
==2759==    by 0x11387C: initLock__coreZlocks_u7 (in /home/lenz/LogSearch/logsd)
==2759==    by 0x1149A1: atmproceduresatstcpServerdotnim_Init000 (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114A98: PreMainInner (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114AA9: PreMain (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114AC1: NimMain (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114B00: main (in /home/lenz/LogSearch/logsd)
==2759==  Address 0x11a360 is 0 bytes inside data symbol "lock__proceduresZtcp83erver_u5"
==2759== 
==2759== Possible data race during write of size 8 at 0x1FFEFFF5B0 by thread #12
==2759== Locks held: none
==2759==    at 0x10B335: threadProcWrapper__proceduresZtcp83erver_u66 (in /home/lenz/LogSearch/logsd)
==2759==    by 0x48568F6: ??? (in /usr/lib64/valgrind/valgrind/vgpreload_helgrind-amd64-linux.so)
==2759==    by 0x4A0645A: start_thread (pthread_create.c:447)
==2759==    by 0x4A92BE3: clone (clone.S:100)
==2759== 
==2759== This conflicts with a previous read of size 8 by thread #1
==2759== Locks held: 1, at address 0x11A360
==2759==    at 0x113977: running__proceduresZtcp83erver_u31 (in /home/lenz/LogSearch/logsd)
==2759==    by 0x11437E: startServer__proceduresZtcp83erver_u11 (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114B4B: NimMainModule (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114AB5: NimMainInner (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114AC6: NimMain (in /home/lenz/LogSearch/logsd)
==2759==    by 0x114B00: main (in /home/lenz/LogSearch/logsd)
==2759==  Address 0x1ffefff5b0 is on thread #1's stack
==2759==  in frame #3, created by startServer__proceduresZtcp83erver_u11 (???:)
==2759==
Laravel.io Logo

Please note that all pasted data is publicly available.

X (fomerly Twitter) GitHub