Re: [Valgrind-valkyrie-dev] [Valgrind-users] XML output for Helgrind?

[Cerion Armour-B. <ce...@ke...>]

Hi Diego,

Sorry for the slow responses. We're finally pushing Valkyrie forward though, 
and expect a beta minor release next week. This will support the latest 
Valgrind release.

We're also starting to think more about the next stage for Valkyrie, and 
people are prodding at porting it to QT4, and wondering whether this implies 
a re-write...

I'm wondering if you made any progress with your Ruby idea?  I don't know much 
about Ruby, but I've heard lots of praise for it.

Something important is what the next generation tool will need to be able to 
support: namely, the other valgind tools: cachegrind, helgrind etc., and what 
kind of functionality it therefore must be able to support: graphics, 
whatever. Is Ruby a better choice than QT? Are you for Ruby because you know 
it better than QT, or does it offer particular advantages?

Cheers,
Cerion


On Monday 17 Dec 2007, Diego 'Flameeyes' Pettenò wrote:
> 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.