OpenTTD.andythenorth(7213)$ valgrind ./bin/openttd
==94051== Memcheck, a memory error detector
==94051== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==94051== Using Valgrind-3.14.0 and LibVEX; rerun with -h for copyright info
==94051== Command: ./bin/openttd
==94051== 
--94051-- run: /usr/bin/dsymutil "./bin/openttd"
warning: no debug symbols in executable (-arch x86_64)
--94051-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option
--94051-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 2 times)
--94051-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 4 times)
--94051-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 8 times)
==94051== Thread 2:
==94051== Invalid read of size 4
==94051==    at 0x109A56E3A: _pthread_wqthread (in /usr/lib/system/libsystem_pthread.dylib)
==94051==    by 0x109A56BE8: start_wqthread (in /usr/lib/system/libsystem_pthread.dylib)
==94051==  Address 0x18 is not stack'd, malloc'd or (recently) free'd
==94051== 
==94051== Invalid read of size 8
==94051==    at 0x109A17AD1: __error (in /usr/lib/system/libsystem_kernel.dylib)
==94051==    by 0x1096DCA4D: puts (in /usr/lib/system/libsystem_c.dylib)
==94051==    by 0x100204A6B: CrashLogOSX::MakeCrashLog() (in ./bin/openttd)
==94051==    by 0x109A56BE8: start_wqthread (in /usr/lib/system/libsystem_pthread.dylib)
==94051==  Address 0x8 is not stack'd, malloc'd or (recently) free'd
==94051== 
==94051== 
==94051== Process terminating with default action of signal 11 (SIGSEGV)
==94051==  Access not within mapped region at address 0x8
==94051==    at 0x109A17AD1: __error (in /usr/lib/system/libsystem_kernel.dylib)
==94051==    by 0x1096DCA4D: puts (in /usr/lib/system/libsystem_c.dylib)
==94051==    by 0x100204A6B: CrashLogOSX::MakeCrashLog() (in ./bin/openttd)
==94051==    by 0x109A56BE8: start_wqthread (in /usr/lib/system/libsystem_pthread.dylib)
==94051==  If you believe this happened as a result of a stack
==94051==  overflow in your program's main thread (unlikely but
==94051==  possible), you can try to increase the size of the
==94051==  main thread stack using the --main-stacksize= flag.
==94051==  The main thread stack size used in this run was 8388608.
--94051:0:schedule VG_(sema_down): read returned -4

valgrind: m_scheduler/scheduler.c:931 (void run_thread_for_a_while(HWord *, Int *, ThreadId, HWord, Bool)): Assertion 'VG_(stats__n_xindirs_32) == 0' failed.

host stacktrace:
==94051==    at 0x2580412B1: ???
==94051==    by 0x258041616: ???
==94051==    by 0x2580415F6: ???
==94051==    by 0x2580B73E9: ???
==94051==    by 0x2580B5676: ???
==94051==    by 0x2580C6A53: ???
==94051==    by 0x2580C6D10: ???

sched status:
  running_tid=1

Thread 1: status = VgTs_Runnable (lwpid 5635)
==94051==    at 0x109A56BDC: start_wqthread (in /usr/lib/system/libsystem_pthread.dylib)
client stack range: ??????? client SP: 0x700006727F80
valgrind stack range: [0x700000CBA000 0x700000DB9FFF] top usage: 9784 of 1048576

Thread 2: status = VgTs_Yielding (lwpid 4107)
==94051==    at 0x109A17AD1: __error (in /usr/lib/system/libsystem_kernel.dylib)
==94051==    by 0x1096DCA4D: puts (in /usr/lib/system/libsystem_c.dylib)
==94051==    by 0x100204A6B: CrashLogOSX::MakeCrashLog() (in ./bin/openttd)
==94051==    by 0x109A56BE8: start_wqthread (in /usr/lib/system/libsystem_pthread.dylib)
client stack range: ??????? client SP: 0x7000066926B8
valgrind stack range: [0x7000053A6000 0x7000054A5FFF] top usage: 4920 of 1048576


Note: see also the FAQ in the source distribution.
It contains workarounds to several common problems.
In particular, if Valgrind aborted or crashed after
identifying problems in your program, there's a good chance
that fixing those problems will prevent Valgrind aborting or
crashing, especially if it happened in m_mallocfree.c.

If that doesn't help, please report this bug to: www.valgrind.org

In the bug report, send all the above text, the valgrind
version, and what OS and version you are using.  Thanks.