https://bugs.kde.org/show_bug.cgi?id=362223
--- Comment #1 from nickolayzho...@gmail.com --- -Attention! -The version of valgrind is 3.10.1 and full message was: valgrind: m_commandline.c:77 (read_dot_valgrindrc): Assertion 'n >= 0 && n <= stat_buf.size+1' failed. host stacktrace: ==10093== at 0x3805DB16: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) sched status: running_tid=0 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. -For the 3.11.0 message was one line, represented in first report. -- You are receiving this mail because: You are watching all bug changes.
