https://bugs.kde.org/show_bug.cgi?id=424656
--- Comment #2 from Rick Stanley <rstan...@rsiny.com> --- Is there a way to suppress a valgrind warning in the code for specific lines and/or functions by setting/un-setting a variable or using comment lines? If not then there should be. In the real code I am writing, I want to simply display in hex the values of each byte of an allocation irregardless of all the bytes being initialized or not. Thank you! On Sat, 2020-07-25 at 15:11 +0000, Philippe Waroquiers wrote: > https://bugs.kde.org/show_bug.cgi?id=424656 > > Philippe Waroquiers <philippe.waroqui...@skynet.be> changed: > > What |Removed |Added > ------------------------------------------------------------------- > --------- > CC| > |philippe.waroquiers@skynet. > | |be > > --- Comment #1 from Philippe Waroquiers < > philippe.waroqui...@skynet.be> --- > That looks like a real bug that valgrind detects. > > The malloc allocates 32 bytes, the strcpy initialises 16 bytes > but the printf loop prints the 32 bytes, so effectively prints data > nopt > initialised. > -- You are receiving this mail because: You are watching all bug changes.
