https://bugs.kde.org/show_bug.cgi?id=511717
--- Comment #4 from Paul Floyd <[email protected]> --- OK thanks. I had to guess a bit as to which valgrind_read_memory it was being called. In the code decode_m_packet (&own_buf[1], &mem_addr, &len); if (valgrind_read_memory (mem_addr, mem_buf, len) == 0) { That's reading len bytes from mem_addr to mem_buf. The assert shows that mem_buf is big enough to accept len bytes. So it looks to me as though mem_addr is wrong. Perhaps there is an issue decoding the packet? -- You are receiving this mail because: You are watching all bug changes.
