Loading

Paste #pgtcjzyqf

Wrap Raw Revise
  1. OpenTTD.andythenorth(7213)$ valgrind ./bin/openttd
  2. ==94051== Memcheck, a memory error detector
  3. ==94051== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
  4. ==94051== Using Valgrind-3.14.0 and LibVEX; rerun with -h for copyright info
  5. ==94051== Command: ./bin/openttd
  6. ==94051==
  7. --94051-- run: /usr/bin/dsymutil "./bin/openttd"
  8. warning: no debug symbols in executable (-arch x86_64)
  9. --94051-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option
  10. --94051-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 2 times)
  11. --94051-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 4 times)
  12. --94051-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 8 times)
  13. ==94051== Thread 2:
  14. ==94051== Invalid read of size 4
  15. ==94051==    at 0x109A56E3A: _pthread_wqthread (in /usr/lib/system/libsystem_pthread.dylib)
  16. ==94051==    by 0x109A56BE8: start_wqthread (in /usr/lib/system/libsystem_pthread.dylib)
  17. ==94051==  Address 0x18 is not stack'd, malloc'd or (recently) free'd
  18. ==94051==
  19. ==94051== Invalid read of size 8
  20. ==94051==    at 0x109A17AD1: __error (in /usr/lib/system/libsystem_kernel.dylib)
  21. ==94051==    by 0x1096DCA4D: puts (in /usr/lib/system/libsystem_c.dylib)
  22. ==94051==    by 0x100204A6B: CrashLogOSX::MakeCrashLog() (in ./bin/openttd)
  23. ==94051==    by 0x109A56BE8: start_wqthread (in /usr/lib/system/libsystem_pthread.dylib)
  24. ==94051==  Address 0x8 is not stack'd, malloc'd or (recently) free'd
  25. ==94051==
  26. ==94051==
  27. ==94051== Process terminating with default action of signal 11 (SIGSEGV)
  28. ==94051==  Access not within mapped region at address 0x8
  29. ==94051==    at 0x109A17AD1: __error (in /usr/lib/system/libsystem_kernel.dylib)
  30. ==94051==    by 0x1096DCA4D: puts (in /usr/lib/system/libsystem_c.dylib)
  31. ==94051==    by 0x100204A6B: CrashLogOSX::MakeCrashLog() (in ./bin/openttd)
  32. ==94051==    by 0x109A56BE8: start_wqthread (in /usr/lib/system/libsystem_pthread.dylib)
  33. ==94051==  If you believe this happened as a result of a stack
  34. ==94051==  overflow in your program's main thread (unlikely but
  35. ==94051==  possible), you can try to increase the size of the
  36. ==94051==  main thread stack using the --main-stacksize= flag.
  37. ==94051==  The main thread stack size used in this run was 8388608.
  38. --94051:0:schedule VG_(sema_down): read returned -4
  39.  
  40. 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.
  41.  
  42. host stacktrace:
  43. ==94051==    at 0x2580412B1: ???
  44. ==94051==    by 0x258041616: ???
  45. ==94051==    by 0x2580415F6: ???
  46. ==94051==    by 0x2580B73E9: ???
  47. ==94051==    by 0x2580B5676: ???
  48. ==94051==    by 0x2580C6A53: ???
  49. ==94051==    by 0x2580C6D10: ???
  50.  
  51. sched status:
  52.   running_tid=1
  53.  
  54. Thread 1: status = VgTs_Runnable (lwpid 5635)
  55. ==94051==    at 0x109A56BDC: start_wqthread (in /usr/lib/system/libsystem_pthread.dylib)
  56. client stack range: ??????? client SP: 0x700006727F80
  57. valgrind stack range: [0x700000CBA000 0x700000DB9FFF] top usage: 9784 of 1048576
  58.  
  59. Thread 2: status = VgTs_Yielding (lwpid 4107)
  60. ==94051==    at 0x109A17AD1: __error (in /usr/lib/system/libsystem_kernel.dylib)
  61. ==94051==    by 0x1096DCA4D: puts (in /usr/lib/system/libsystem_c.dylib)
  62. ==94051==    by 0x100204A6B: CrashLogOSX::MakeCrashLog() (in ./bin/openttd)
  63. ==94051==    by 0x109A56BE8: start_wqthread (in /usr/lib/system/libsystem_pthread.dylib)
  64. client stack range: ??????? client SP: 0x7000066926B8
  65. valgrind stack range: [0x7000053A6000 0x7000054A5FFF] top usage: 4920 of 1048576
  66.  
  67.  
  68. Note: see also the FAQ in the source distribution.
  69. It contains workarounds to several common problems.
  70. In particular, if Valgrind aborted or crashed after
  71. identifying problems in your program, there's a good chance
  72. that fixing those problems will prevent Valgrind aborting or
  73. crashing, especially if it happened in m_mallocfree.c.
  74.  
  75. If that doesn't help, please report this bug to: www.valgrind.org
  76.  
  77. In the bug report, send all the above text, the valgrind
  78. version, and what OS and version you are using.  Thanks.
Posted by Anonymous at 20 Feb 2019, 08:13:56 UTC
Language: text • Views: 734

Comments