https://bugs.kde.org/show_bug.cgi?id=434057
Pedro Alves <pe...@palves.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pe...@palves.net
--- Comment #3 from Pedro Alves <pe...@palves.net> ---
(In reply to Philippe Waroquiers from comment #1)
> A possible implementation might be a new vgdb option such as:
> --valgrind [VALGRIND_OPTIONS ...] PROGRAM_TO_RUN_UNDER_VALGRIND
> [PROGRAM_ARGS ...]
>
> When vgdb gets this argument, it would launch valgrind itself and connect to
> it.
An alternative, or extension to the idea, would be to have a "vgdb --multi"
(similar to gdbserver --multi, but name it however you wish), and make vgdb not
start valgrind until the user types "run". You'd likely want to decouple this
from 'socket vs stdio', so you'd have something like:
(gdb) target extended-remote | vgdb --stdio --multi
PROGRAM_TO_RUN_UNDER_VALGRIND
(gdb) set args foo bar
(gdb) run
this way, re-running the program is just another "run".
--
You are receiving this mail because:
You are watching all bug changes.
