https://bugs.kde.org/show_bug.cgi?id=435665
--- Comment #8 from Tulio Magno Quites Machado Filho <tul...@quites.com.br> --- (In reply to Julian Seward from comment #5) > there's no way to tell Memcheck > or any other tool, that the values in the destination area are > derived from values in the source area. So you'll wind up with > definedness false positives or negatives as a result of using them. Yes. I think the user will always have to ignore at least one false positive when the program tries to read the memory from the accelerator, regardless if copy/paste is being used. (In reply to Julian Seward from comment #7) > I'd say the least worst is to implement it so that, for the copy, > Memcheck will flag an error if any of the 128 bytes are undefined, > and for the paste we make it look as if the 128 bytes are > completely defined. That way, at least you'll know if you're > sending undefined values to the accelerator. As someone that plans to use this feature, I'd say the minimum I expect is that Valgrind doesn't abort when copy/paste/cpabort is used. But getting extra errors like these would be great indeed. -- You are receiving this mail because: You are watching all bug changes.
