Bug 146242

Summary:	GDB integration for Valgrind
Product:	[Applications] kdevelop	Reporter:	Dave Baker <davidbaker84>
Component:	Plugin: Valgrind integration	Assignee:	kdevelop-bugs-null
Status:	CONFIRMED ---
Severity:	wishlist	CC:	aspotashev
Priority:	NOR
Version First Reported In:	git master
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Dave Baker 2007-06-01 10:40:47 UTC

Version:           SVN (using KDE KDE 3.5.7)
Installed from:    Gentoo Packages
OS:                Linux

It would be incredibly useful if kdevelop's valgrind frontend could use valgrind's --db-attach option to launch a GDB which would then be attatched to kdevelop's GDB frontend. Presumably there would be an extra option in the Valgrind run dialog to request that a prompt be displayed on each error asking whether to attatch the debugger.

Comment 1 Andreas Pakulat 2008-07-01 22:53:15 UTC

can you elaborate a bit on the use-case for this?

Comment 2 Matt Rogers 2008-07-01 23:12:34 UTC

valgrind can be set up to ask the user if they want to attach a debugger when an error is encountered. We would need to handle that and then attach the running process using KDevelop's GDB integration.

Comment 3 Dave Baker 2008-07-02 11:59:14 UTC

The use case would be that the user starts their program in valgrind using KDevelop's valgrind integration and then when Valgrind finds a problem, a message would be displayed asking if the user whishes to attatch a debugger. If the user clicks 'yes', gdb will run and KDevelop's GDB integration would start up. The user can then inspect the state of their program a diagnose the problem. Once they are finished, they can either stop the debugger and Valgrind can continue running, or stop the program altogether, ending both the Valgrind and the debugger session.