gcc8 has extended array out-of-bounds access warnings, and the memcpy call in rP18423 triggers this:
In file included from /usr/include/string.h:635, from /usr/include/c++/8/cstring:42, from /usr/include/boost/filesystem/path.hpp:36, from /usr/include/boost/filesystem.hpp:16, from ../../../source/lib/pch/pch_boost.h:57, from ../../../source/lib/precompiled.h:76, from ../../../source/pch/engine/precompiled.h:18: In function ‘void* memcpy(void*, const void*, size_t)’, inlined from ‘void rewriteBuffer(u8*, u32&)’ at ../../../source/ps/Profiler2.cpp:564:10: /usr/include/x86_64-linux-gnu/bits/string3.h:53:33: warning: ‘void* __builtin___memcpy_chk(void*, const void*, long unsigned int, long unsigned int)’ forming offset [257, 4294967295] is out of the bounds [0, 256] of object ‘message’ with type ‘char [256]’ [-Warray-bounds] return __builtin___memcpy_chk (__dest, __src, __len, __bos0 (__dest)); ~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ../../../source/ps/Profiler2.cpp: In function ‘void rewriteBuffer(u8*, u32&)’: ../../../source/ps/Profiler2.cpp:563:9: note: ‘message’ declared here char message[CProfiler2::MAX_ATTRIBUTE_LENGTH] = {0}; ^~~~~~~
The warning should vanish one way or the other.
The warning was fixed in rP22624 but that code does not build in debug mode for a reason unknown to me.