https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113045
--- Comment #18 from David Binderman <dcb314 at hotmail dot com> --- (In reply to Mark Wielaard from comment #17) > I am surprised valgrind memcheck doesn't produce more output, normally it > would tell you why & where it found the address invalid. The valgrind output I gave originally looks to be in the usual valgrind format to me. Perhaps you are assuming some other debugging tool like asan or ubsan ? > I assume somehow > valgrind memcheck believes it is reading past the end of a data buffer, > while the code assumes this is fine because it will mask off the bits it > won't use. valgrind doesn't normally produce an error for copying around un-initialised bytes. However, it will produce an error if those bytes are used in a decision like an if statement. Your unconfirmed assumption agrees with mine, though.
