Bug 374850 - The Impossible Happened
Summary: The Impossible Happened
Status: RESOLVED DUPLICATE of bug 375171
Alias: None
Product: valgrind
Classification: Developer tools
Component: memcheck (show other bugs)
Version: 3.12.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Julian Seward
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-10 01:26 UTC by Brandon
Modified: 2017-01-19 16:20 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Valgrind output log (37.95 KB, text/x-log)
2017-01-10 01:26 UTC, Brandon 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Brandon 2017-01-10 01:26:57 UTC 
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
Comment 1 Brandon 2017-01-10 01:30:07 UTC 
My application is 32bit
I'm running XUbuntu

$ cat /etc/issue
Ubuntu 16.04.1 LTS \n \l
Comment 2 Ivo Raisr 2017-01-10 06:53:29 UTC 
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
Comment 3 Brandon 2017-01-10 13:40:40 UTC 
Is there something specific you'd like me to do?

I'm not sure what any of that means.
Comment 4 Brandon 2017-01-19 15:54:11 UTC 
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?
Comment 5 Julian Seward 2017-01-19 16:18:43 UTC 
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?
Comment 6 Tom Hughes 2017-01-19 16:19:29 UTC 
Looks like the same as 375171?
Comment 7 Tom Hughes 2017-01-19 16:20:24 UTC 
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 ***