|
From: <fla...@gm...> - 2007-12-17 21:43:53
|
Hi, I started trying to work on a Ruby frontend for Valgrind, hoping that the most difficult task was to parse the XML properly, but it seems like only memcheck supports XML output. Now the simplest way is to write a parser of the helgrind output, but I'd see as more "proper" way to actually implement XML output in helgrind, if that's acceptable. So the question is, if I spend some time to implement XML output in Helgrind, would it be acccepted and maintained afterward (for instance if new output is added)? I can't promise anything, but as I consider valgrind an important tool in xine's development, I'd gladly take some time off xine to work on it. =2D-=20 Diego "Flameeyes" Petten=C3=B2 http://farragut.flameeyes.is-a-geek.org/ |
|
From: Nicholas N. <nj...@cs...> - 2007-12-17 21:46:11
|
On Mon, 17 Dec 2007, Diego 'Flameeyes' [utf-8] Petten=F2 wrote: > I started trying to work on a Ruby frontend for Valgrind, Is this a GUI front-end? If so, you should look at=20 http://www.valgrind.org/downloads/guis.html if you haven't already. Or do you mean something else? Nick |
|
From: <fla...@gm...> - 2007-12-17 21:57:19
|
Nicholas Nethercote <nj...@cs...> writes: > Is this a GUI front-end? If so, you should look at > http://www.valgrind.org/downloads/guis.html if you haven't already. I actually know them already, and I've used Valkyrie up to now as memcheck frontend. Problem with Valkyrie is that it doesn't work with Valgrind 3.3.0, the development is stopped since August 2006, and I didn't see all of the patches I sent some time ago to the project applied at the moment, which makes me think that patching it again will be hopeless. My idea was to actually write a Ruby library for valgrind interaction, and then build one or more interfaces on top of that. =2D-=20 Diego "Flameeyes" Petten=C3=B2 http://farragut.flameeyes.is-a-geek.org/ |
|
From: Julian S. <js...@ac...> - 2007-12-18 12:00:20
|
> I actually know them already, and I've used Valkyrie up to now as > memcheck frontend. Problem with Valkyrie is that it doesn't work with > Valgrind 3.3.0, Urr. I didn't know that - I thought the 3.3.0 XML output changes would have no effect. Can you summarise the way(s) in which Valkyrie does not work with Valgrind 3.3.0 ? > the development is stopped since August 2006, and I > didn't see all of the patches I sent some time ago to the project > applied at the moment, which makes me think that patching it again will > be hopeless. I'll look into that. Sorry for the patch lossage. Regarding your original comments (re Helgrind XML output). I think this is a good idea. However, Helgrind is still in a state of change and I envisage that the error message formats will change early next year, so it might be better to wait a little while first. J |