[Valgrind-users] Removal of db-attach

[Maurice v. d. P. <gri...@kf...>]

I know I'm quite late with this. I only just found the information about
deprecation of --db-attach in the changelog and Florian's message about
it to this list in July of this year.

Nevertheless, I have to say that the removal of --db-attach is in my
opinion quite a step back from a usability perspective.

Valgrind has always been the one program of its kind that you could just
run on an executable that you already had and would immediately give
useful results. It has sensible defaults that keep the number of command
line options you need to specify down to a minimum.

Unfortunately the removal of --db-attach seems to make things less
convenient.

In the past I had to do the following for a simple session:
* specify a single command line option
* press n or y to continue or debug

Now I have to:
* specify a command line option
* open a second terminal
* type the full path to my executable (or navigate there) and start gdb
* type target remote | vgdb
* switch to the original terminal to check what error was given
* switch back to the gdb terminal to continue or debug

I appreciate that the built-in gdb server is an improvement over the
previous solution, but is it not possible to keep the user experience as
easy as before? If valgrind could launch gdb in the same terminal and
connect it to itself that would make the (for me) common case as easy as
it was before.

Best regards,
Maurice.

-- 
Maurice van der Pot

Kdiff3 developer   gri...@kf...   http://kdiff3.sourceforge.net
Tdiff3 developer                            https://github.com/Griffon26/tdiff3