|
From: Foster, G. <gar...@si...> - 2005-04-28 08:46:51
|
Hello Robert, Nicholas, Thank you both for your replies. I'll try and collate the information from both and ask some further questions. > Should be doable. Someone just needs to find the time. Since I don't > think any of the current developers uses an IDE like Anjuta or Eclipse, > I suspect it will be a low priority RFE. I didn't mean to imply that any of the Valgrind developers would have time for this, rather that I would try to drum up some interest in the idea in the Gnome/GTK+ community, and more specifically in the Anjuta team. > What do you mean by "similar setup"? Do you just want to > invoke Valgrind > conveniently from within the IDE, or are you thinking of some > kind of GUI? > I was just thinking of the sort of integration into Anjuta that you see between Purify and VC++. What it does is embed itself in the IDE, so you can invoke it conveniently like you said, but it goes a little further than that perhaps implies, for example warnings pop up as you debug, and there is a general report of problems and issues at the end of a debugging run, all of this integrated into the IDE UI. So its sort of both of the above, only that the IDE is the GUI, hopefully that makes sense. > I believe KDevelop has a Valgrind plug-in, but I don't know > how it works. > I am sure that would be worth investigating. So, knowing that people have managed a similar effort in integration into an IDE, and knowing the level of integration I thought would be nice (i.e that level I described when discussing Purify), how does the following statement impact on the idea in general? > No - Valgrind isn't really used like that. Since it's a virtual > machine, it takes over execution of the process entirely. Valgrind used > to be implemented as a shared library that got injected before your main > program, but that caused too many problems and we changed over to a > complete virtual machine instead. Thanks again for information already supplied, and thanks in advance for any further information, it is much appreciated, Regards, Gaz |
|
From: Nicholas N. <nj...@cs...> - 2005-04-28 12:29:46
|
On Thu, 28 Apr 2005, Foster, Gareth wrote: > So, knowing that people have managed a similar effort in integration into an > IDE, and knowing the level of integration I thought would be nice (i.e that > level I described when discussing Purify), how does the following statement > impact on the idea in general? > >> No - Valgrind isn't really used like that. Since it's a virtual >> machine, it takes over execution of the process entirely. Valgrind used >> to be implemented as a shared library that got injected before your main >> program, but that caused too many problems and we changed over to a >> complete virtual machine instead. Here's how I imagine the KDevelop plug-in works: you invoke Valgrind somehow, and KDevelop works out what options to pass to Valgrind, then runs Valgrind (and the user program under it), then collects the output somehow, parses it, and presents it to the programmer in the IDE somehow. So basically Valgrind doesn't need any changes, and there's no need for a Valgrind library or anything like that. In principle an IDE could do this with almost any batch program, it just needs to manage the inputs and the outputs. N |
|
From: Brett K. <br...@la...> - 2005-04-28 13:21:29
|
Hi all, I usually just passively read selected posts here, but this is an area of interest to me and my organization. For some time now Los Alamos National Lab (LANL), Lawrence Livermore National Lab (LLNL), and Sandia National Lab (SNL) have combined forces to support work by OpenWorks in its effort to spread Valgrind and its tools to other platforms and support for a wide variety of compilers in the Linux environment. Additionally, we'll be adding support for use on MPI-based parallel applications. Julian and Nick have done great work here. >>What do you mean by "similar setup"? Do you just want to >>invoke Valgrind >>conveniently from within the IDE, or are you thinking of some >>kind of GUI? >> > > > I was just thinking of the sort of integration into Anjuta that you see > between Purify and VC++. What it does is embed itself in the IDE, so you can > invoke it conveniently like you said, but it goes a little further than that > perhaps implies, for example warnings pop up as you debug, and there is a > general report of problems and issues at the end of a debugging run, all of > this integrated into the IDE UI. So its sort of both of the above, only that > the IDE is the GUI, hopefully that makes sense. This type of IDE integration is something that is of great interest to us at LANL. We have launched a project called the Eclipse Parallel Tools Platform (see http://www.eclipse.org/ptp/). Valgrind-based tools being integrated into this environment would be of interest to us. To start, doing an Eclipse Rich Client Interface for them would be great. This would allow them to be used as standalone tools with GUIs or used as plugins to the Eclipse IDE. We're always looking for folks who are interested in collaborating on projects like this with us. If this would be of interest to you, please contact me directly. Thanks, Brett -- Brett Kettering, LANL correspondence, or Unclassified by DUSA LACSI-CS, or Unclassified by DUSA LACSI-OS |