https://bugs.kde.org/show_bug.cgi?id=434057
--- Comment #22 from Tom Tromey <t...@tromey.com> --- (In reply to Paul Floyd from comment #21) > I also tried to make the startup even easier and after searching a bit and > getting some info on SO I came up with I don't know the exact problem here -- I don't use "extended-remote" much if at all -- but we could write a new "target valgrind" command in Python (shipped with valgrind) that automates some of this. > eval "set remote exec-file %s", $programname Like this bit could be done automatically. Though it occurs to me that it might be even nicer to give gdb some mode like "gdbserver but we know it shares the filesystem", so that "remote exec-file" and "sysroot" aren't needed at all. > I can't find an easy way to get the inferior in gdb (in general there isn't > always just one). Shenanigans with "pipe" and "info inferiors", or gdb.selected_inferior() in Python. > Again I don't know how to do it, but this gdb function would be nicer if > there's a way to pass args to the vgdb line to pass on to valgrind. I would have thought this was handled by extended-remote? Unless you mean some kind of valgrind-specific args, not args to the inferior? The latter could be done by the putative "target valgrind" easily - it could parse its own arguments and do whatever it likes. -- You are receiving this mail because: You are watching all bug changes.
