https://bugs.kde.org/show_bug.cgi?id=434057
Mark Wielaard <m...@klomp.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #29 from Mark Wielaard <m...@klomp.org> ---
commit 0432ce486d61f84f6fcbeab0d812bb1f61c57561
Author: Alexandra Petlanova Hajkova <ahajk...@redhat.com>
Date: Thu Mar 3 04:46:03 2022 -0500
vgdb: implement the extended-remote protocol
Executing vgdb --multi makes vgdb talk the gdb extended-remote
protocol. This means that the gdb run command is supported and
vgdb will start up the program under valgrind. Which means you
don't need to run gdb and valgrind from different terminals.
Also vgdb keeps being connected to gdb after valgrind exits. So
you can easily rerun the program with the same breakpoints in
place.
vgdb now implements a minimal gdbserver that just recognizes
a few extended-remote protocol packets. Once it starts up valgrind
it sets up noack and qsupported then it will forward packets
between gdb and valgrind gdbserver. After valgrind shutsdown it
resumes handling gdb packets itself.
https://bugs.kde.org/show_bug.cgi?id=434057
Co-authored-by: Mark Wielaard <m...@klomp.org>
--
You are receiving this mail because:
You are watching all bug changes.
