https://bugs.kde.org/show_bug.cgi?id=434057
--- Comment #4 from Mark Wielaard <m...@klomp.org> --- We have been looking at this and for the valgrind side it would involve something like Pedro suggests in comment #3. So vgdb would intercept the extended-remote packages (which aren't currently implemented in the valgrind gdbserver) and on an Run packet it would launch valgrind (and connect to it). As a bonus one could implement the multiprocess extensions so it would be easier to follow child processes when valgrind uses --track-children=yes. This is only half of the work though. Although you can change the way gdb and vgdb communicate (it doesn't need to be through stdio, but we could also add a "normal" socket communication channel). We also need a way for gdb and the valgrind process launched through vgdb to share a tty stdin/stdout. This needs an extension to the way a "local" remote process is launched. We cannot use stdin/stdout for the gdb/vgdb communication if we want to start valgrind within vgdb, and have valgrind's in/out share with gdb's tty. So this probably means a special way to start an extended-remote target on the gdb side. -- You are receiving this mail because: You are watching all bug changes.
