|
From: Julian S. <js...@ac...> - 2005-11-05 23:10:50
|
> That is all good and fine, but VGs history tells me: there was not one > tool being accepted to be included into VG unless the author was one > of the VG core authors itself. And there is a reason: if the author > disappears, all the maintenance falls back to the core developers. > And at such a point, it is better to drop it again. This even happened > to one tool from a core developer: helgrind. And that was even "only" > because of changed funtionality of VG core. That really was only because of the threading changes in 2.4, which were carried into 3.0, made it impossible for Helgrind to work. I for one would love to have Helgrind working again. We do get a number of requests for it, and assuming it is possible to make function wrapping work again in the 3.1->3.2 gap, then we might have Helgrind for 3.2. Your best short term course of action, IMO, is to make Omega work really well with 3.1. "work really well" means something like: is able to run programs the size of OpenOffice and Firefox stably, on x86, amd64 and ideally ppc32, in reasonable time, and produces output which is meaningful to users (eg, not many false positives and not many false negatives). Perhaps we should raise the visibility of external tools on the web site by creating a separate page for them off the top level "Information" category. I'd be happy for Omega to be listed there. J |