| Summary: | The Impossible Happened | ||
|---|---|---|---|
| Product: | [Developer tools] valgrind | Reporter: | Brandon <caibbor> |
| Component: | memcheck | Assignee: | Julian Seward <jseward> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | ivosh, tom |
| Priority: | NOR | ||
| Version: | 3.12.0 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | Valgrind output log | ||
My application is 32bit I'm running XUbuntu $ cat /etc/issue Ubuntu 16.04.1 LTS \n \l Assertion on VG_TRC_INVARIANT_FAILED was hit. Further debugging will be required to determine exactly what invariant failed. dispatch-x86-linux.S checks both %mxcsr and %fpucw Is there something specific you'd like me to do? I'm not sure what any of that means. Is there any other information or steps you'd like me to take in order to get the ball rolling on getting this bug fixed? Oh, wait. This got discussed the other day. The conclusion is that it is basically a kernel bug that only manifests on Skylake processors. Are you running on Skylake? Looks like the same as 375171? Most of the discussion is on the other bug so lets keep that open and close this one as a dupe... *** This bug has been marked as a duplicate of bug 375171 *** |
Created attachment 103323 [details] Valgrind output log This happened with 3.11.0 as well as 3.12.0 full output log is attached. here's some other info: $ uname -a Linux antic-Inspiron-7559 4.9.0-040900rc8-generic #201612051443 SMP Mon Dec 5 19:45:51 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux $ valgrind --version valgrind-3.12.0.SVN $ dpkg -l | grep valgrind -i ii libtsan0:amd64 6.2.0-3ubuntu11~16.04 amd64 ThreadSanitizer -- a Valgrind-based detector of data races (runtime) ii valgrind 1:3.12.0~svn20160714-1ubuntu1 amd64 instrumentation framework for building dynamic analysis tools