https://bugs.kde.org/show_bug.cgi?id=381162
--- Comment #13 from Philippe Waroquiers <philippe.waroqui...@skynet.be> --- (In reply to Julian Seward from comment #6) > (In reply to Philippe Waroquiers from comment #5) > > In the particular case of the lib VEX 'fast allocator', there is > > no instrumentation of this allocator [..] > > Ah. Good point. Hmm. Given that VEX is a big(ish) and complex bit of > code, and that it will be getting more complex with Ivo's IR work, it would > be nice if we could Memcheck it properly. In particular I'd like to be able > to check for uninitialised value uses in it. Is it possible you could make > a patch to do what you said, at some point? Yes, I will take a look. Note that this might slow down heavily the inner operations, as any VEX allocate will imply significantly heavier work : take a stack trace, record it, etc ... I will watch the impact (of course, no impact expected unless configured as an inner valgrind) -- You are receiving this mail because: You are watching all bug changes.
