Re: [Valgrind4win-developers] project status

[Jiří H. <ji...@fu...>]

Hi Julian,

> Having some progress on this would be great.
> Is there anything specific that can be done to help move this along?
Well, the project has been more or less idle for the past months...
The other guy has been apparently busy as me and everybody else and
I've been dealing with a single issue - there were a lot of problems
just because of bad symbols (useless reports due to wrong stack
traces, mismatched redirections, crashes due to unknown file format,
pulling a big DLL with many dependencies just to find the .pdb file
path), so I've been working on a proper PDB reader. It's not finished
yet, but I'd call it the most accurate non-MS PDB implementation out
there already.

My understanding of the other parts of the port got a bit rusty in the
meantime, but I will probably have some more free time in the upcoming
weeks, maybe even this weekend, so I'll try to make an updated
overview of what's working, what needs to be (re)done etc., so it is
possible to coordinate further work and know what's missing from at
least an alpha-quality release.

One problem even in the long term might be that there are probably not
too many hackers understanding a bit of all, Valgrind architecture,
assembler, reverse engineering, Windows internals etc. AND enough time
on their hands to get involved. The commit log and me being the only
one active on this mailing list at the moment speaks for itself.
Hopefully when the low-level stuff is done, there will be smaller and
more mundane tasks than "implement kernel callbacks" for more people
to contribute. For me personally, this is maybe the most interesting
project I've been dealing with in the long time and I would love to
devote more to it, but it's been just hard to find the time for it
recently. Maybe I should find some big company which would like to see
this through as a sponsor, heh.

> I was also wondering if it might not be better to use the main V dev
> list for discussions.
Yes, that might be a good idea, there is little going on here anyway.
When I'll make that some kind of a report, I'll crosspost it there.
Of course any discussions about the proper implementation of the
individual parts the port, possible upstream merge etc. are naturally
fit for the main V-dev list or IRC too.

Jiri