Re: [Live-devel] Invalid read in HandleCmd_DESCRIBE

Hi Mr. Finlayson, https://drive.google.com/file/d/1quP_2ZYA1metNSxyM4xSlSqkF2OWSykY/view?usp=sharing I am sending you link to a docker container, containing the aforementioned crashing version, where the bug

Re: [Live-devel] Invalid read in HandleCmd_DESCRIBE

> On Jun 8, 2023, at 9:24 PM, Meng Ruijie wrote: > > We used the address sanitizer to reproduce this bug again. The following is > the bug report. We also attached the relevant files, and you can reproduce > this bug based on the README. Thank you for the instructions on how to reproduce the

Re: [Live-devel] Invalid read in HandleCmd_DESCRIBE

> On Jun 8, 2023, at 5:08 PM, Meng Ruijie wrote: > > Hi, > > We found one memory issue No you didn’t. You ran “valgrind”, and it said that there was an “invalid read”. But you didn’t find out whether or not this report was real (“valgrind” is often mistaken), and, even if it is real, what

[Live-devel] Invalid read in HandleCmd_DESCRIBE

Hi, We found one memory issue about an invalid read in the function handleCmd_DECRIBE in live.2023.05.10. Here is the bug report from the Valgrind: --- ==1744== Invalid read of size 1 ==1744==at 0x483EF46: strlen (in /usr/lib/x86_64-linux-gnu/valgrind/vgpreload_memcheck-amd64-linux.so) ==1