Hi all,
I think the 3.8.0 release is a good occasion to give you an update on
the Valgrind for Windows development effort.
Since its inception last November, significant progress has been made.
But it is still a long way to go. So I'm calling again for any
interested developers to join the project.
The Valgrind for Windows code is now in synch with the 3.8.0 release.
Valgrind including all tools (except the two pthread error detectors),
as well as many test programs, build on Windows in both 32 and 64 bit
versions.
Simple applications can be run, compiled with MSVC or GCC, even GUI ones
("MessageBox"). Memory errors (buffer overruns, uninitialized memory,
memory leaks) are detected for 32 bit apps. The instrumentation, system
calls -including callbacks from system calls-, function redirection,
work in principle.
The biggest issues right now are stability and making progress in the
following areas:
1. debug information parsing, especially PDB, especially 64 bit
2. stack walking, both 32 and 64 bit
3. function redirection on 64 bit (32 bit seems to work)
Bugs such as Valgrind crashing because it might not properly read PDB
symbol information impede further progress (see
http://sourceforge.net/p/valgrind4win/tickets/17/)
There are other items on the list, please see the project homepage on
SourceForge: http://sourceforge.net/projects/valgrind4win/
Thanks for your interest, and thank you Julian and the other developers
for another great Valgrind release.
Chris
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
