Valgrind in KDevelop

[Harald Fernengel]

Hi,

On Wednesday 20 March 2002 09:53, Lau Sennels wrote:
> I am unsure wether this is the right list, but here goes.
>
> I think integrating Valgrind into KDevelop would be a valuable addition
> to the program. I'm sure you know Valgrind, but it is a low-level
> source-referencing memory maanager for C/C++. The way I see it, it would
> be used dynamically the samew way the debugger works.
>
> The program is still being developed and I haven't talked to its
> developer, Julian Seward, yet. Also it is currently for x86-
> architectures, but it would definitely enhance the usability of
> KDevelop.

this is on my TODO list. I'm currently thinking of two ways to integrate 
Valgrind into KDevelop:

1. Add it to the tools-menu, pipe the output into the StdOut Window, parse and 
highlight it and allow double-clicking on warnings to jump to the right place 
in code. (for KDevelop 2.x)

2. Convert KValgrind (in kdenonbeta module) into a KPart and integrate it into 
the IDE (for KDevelop 3.x maybe)

The first method should be easier since we are already parsing the output of 
the make command so adding a few Valgrind hooks shouldn't be a problem.

At the moment we have to concentrate to get KDevelop 2.x as stable as 
possible, so I won't start on Valgrind support before KDE3 has been released. 
Any help/comments are greatly appreciated :)

Best regards,
Harry