Valgrind has changed between r12307 (valgrind-variant@r137) and r13132
(v-v@r141).
These changes include API changes that has broken TSan@r4402, failures look
like this:
------------------------------------------------
IR SANITY CHECK FAILURE
IRSB {
t0:I32 t1:I32 t2:I32 t3:I32 t4:I32 t5:I32 t6:I32 t7:I32
t8:I32 t9:I32
------ IMark(0x405DEA0, 1, 0) ------
t0 = GET:I32(28)
t4 = GET:I32(24)
t3 = Sub32(t4,0x4:I32)
PUT(24) = t3
STle(t3) = t0
------ IMark(0x405DEA1, 2, 0) ------
PUT(28) = t3
PUT(68) = 0x405DEA3:I32
------ IMark(0x405DEA3, 5, 0) ------
t6 = Sub32(t3,0x4:I32)
PUT(24) = t6
STle(t6) = 0x405DEA8:I32
t9 = GET:I32(24)
DIRTY 1:I1 ::: evh__rtn_call_ignore_no[rp=2]{0x38069d90}(t9,0x405E490:I32)
PUT(0) = 0x405E490:I32; exit-Call
}
ERROR = bb->offsIP: too low
vex: the `impossible' happened:
sanityCheckFail: exiting due to bad IR
vex storage: T total 15909964 bytes allocated
vex storage: P total 384 bytes allocated
------------------------------------------------
I've rolled back valgrind-variant@r137 as r4403, so the trunk version is the
latest stable version with Ubuntu Lucid support.
Unfortunately, we don't have enough cycles to put into this now,
so Ubuntu Precise won't be supported unless someone takes this task.
See http://code.google.com/p/data-race-test/wiki/HowToContribute if you're
interested.
Original issue reported on code.google.com by timurrrr@google.com on 4 Dec 2012 at 9:34
Original issue reported on code.google.com by
timurrrr@google.com
on 4 Dec 2012 at 9:34