Mirror of forum.nim-lang.org

10005 :: testament + valgrind: importing asyncdispatch or threadpool causes valgrind to throw?

• noah (orginal) [2023-03-15T18:14:49+01:00] view original

  In all my testament specs I set valgrind: true

  however, if I import std/asyncdispatch or std/threadpool into file A

  • e.g. this file

  and then import file A into file B

  • e.g. this file

  it will cause valgrind to throw

  • e.g. this test run

  I looked through the testament docs but did not see anything pertinent to this issue

  • if i set valgrind: "leaks" then the tests will pass, however, this defeats the purpose of using valgrind

---

• Araq (orginal) [2023-03-15T22:19:45+01:00] view original

  Use --mm:orc -d:useMalloc with Valgrind in order to avoid false positives.

---

• noah (orginal) [2023-03-15T22:46:29+01:00] view original

  I ensured both --m:orc and --define:useMalloc were set in both configuration and testament.cmd directive

  unfortunately, all tests still fail if valgrind: true and asyncdispatch / threadpool are imported

---