Howto integrate valgrind

[Aleix Pol]

Why don't we add just memcheck by default and let the user add more actions
if he wants to?

On Sun, May 3, 2009 at 12:25 PM, Andreas Pakulat <apaku at gmx.de> wrote:

> Hi,
>
> I've started to port the valgrind plugin to the launch framework and
> came across a decision on which I'd like some input. Basically its how
> to best integrate the various valgrind tools that are available.
>
> Right now the solution is to have 1 launcher for each tool, and they all
> support the profile mode. This has the benefit of having 1 action in the
> gui to start a valgrind run, on the downside this means when you want to
> switch from memory-profiling to say callgrind you'll need to adjust that
> in the launch configuration (as there's only 1 active launcher per
> launch mode per launch configuration).
>
> The other option is to create new launch modes for each of the tools,
> i.e. profile (memory), profile (function calls), profile (threading)...
> The obvious downside is an explosion of gui actions in the
> menus/toolbars, while on the upside you can easily switch between
> running a memory-profile and a calling-profile.
>
> Opinions?
>
> Andreas
>
> --
> You will gain money by a speculation or lottery.
>
> _______________________________________________
> KDevelop-devel mailing list
> KDevelop-devel at kdevelop.org
> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20090503/1bb9b0d4/attachment.html>