|
From: Julian S. <ju...@va...> - 2005-07-19 13:27:22
|
Over the past year, a tremendous amount of development effort has gone into the Valgrind 3 line. It now runs on x86 and amd64 quite usably, and ppc32 (Linux) is looking promising. There have been a large number of of bug fixes, functionality improvments, and restructuring of the source code to enhance accessibility and maintainability. A GUI (Valkyrie) is also under development, and we plan to make coordinated releases of that along with Valgrind in the future. The time for a Valgrind-3.0 release draws near. I propose to have a release candidate (feature freeze) by next Monday 25 July, with a possible release on Monday 1 Aug. Valgrind-3.0 is already stable and usable on x86 and amd64. If you haven't already done so, please checkout and build it (easy: see http://www.valgrind.org/devel/cvs_svn.html), test it on whatever applications are critical for you, and let us know of any critical breakage. The more people who do this now, the better quality 3.0 release we will have. Outstanding issues which I'm aware of, and which need to be fixed, are: - decide on a version numbering / branch management scheme - decide about how to handle dependency on libvex - minor tweaks to XML output and to logfile naming (me) - fix: #88116 (x86, "enter" variant causes assertion) #96542 (x86, possible assertions with push variants) #87263 (x86, segment stuff) #103594 (x86, FICOM) INT/INT3 insns (x86) Missing 0xA3 insn (amd64) All of these I'll chase. - Update documentation (me, + ??) I'm sure there are other things I've forgotten/am not aware of. Much effort recently has gone into making ppc32-linux work well, but that target is not yet really usable. In particular there are problems with getting a low noise level from Memcheck, and some difficulties with floating point. Work to resolve these is in progress, but I do not know if it will be successful in the limited time before the release. We are already overdue for a 3.0 release and I am reluctant to delay it further in order to have ppc32 support. Therefore I propose to present 3.0 as a production-quality release for x86 and amd64 only, and if ppc32 happens to be usable, well that's an extra bonus. Obviously it would be wonderful to have ppc32 usable too, and I will endeavour to cause that to be the case. So: - pls download, build, test, report critical bugs - JosefW: what is the calltree status for the 3 line? It would be good to ensure that calltree/kcachegrind works well with 3.0. J |