The logical differences under the NDEBUG macro #1204
Description
When compiling the release version of the dll on Windows, this macro is included. It was found that when using memmove under NDEBUG, the output result obtained is problematic.
However, from the following logic, it seems that there might be a logic of mutual stepping on memory. Is this a normal phenomenon? As shown in the figure, the scene of memory overlap will appear in the printed log. The following logic should be that the data cannot be transferred correctly. Why is the result more accurate? It's still my illusion.
