https://bugs.kde.org/show_bug.cgi?id=511717
--- Comment #3 from Libor Peltan <[email protected]> --- Thank you for the quick reply! Indeed, I was able to build valgrind from git sources. Now the version is Valgrind-3.27.0.GIT-85a06581cc-20251106X and the issue reproduces equally. >From the printed "host stacktrace", it rather seems to crash here: case 'x': decode_m_packet (&own_buf[1], &mem_addr, &len); if (valgrind_read_memory (mem_addr, mem_buf, len) == 0) { // Read memory is successful. // Complete the reply packet and indicate its length. int out_len; own_buf[0] = 'b'; new_packet_len = 1 + remote_escape_output(mem_buf, len, (unsigned char *) &own_buf[1], &out_len, PBUFSIZ - POVERHSIZ - 1); } else write_enn (own_buf); break; Anyway, I inserted the vg_assert into both 'case' branches and it doesn't seem to have changed anything. There is still the SIGSEGV crash on the line following the (newly inserted) vg_assert (i.e. inside valgrind_read_memory). -- You are receiving this mail because: You are watching all bug changes.
