On Wed, 2008-07-02 at 10:57 -0500, James Hawkins wrote:
On Wed, Jul 2, 2008 at 9:40 AM, Dan Kegel dank@kegel.com wrote:
Hi James, could you have a look at yet more fresh valgrind warnings, triggered by http://source.winehq.org/git/wine.git/?a=commit;h=d9ac95be5bb51de2293326920c... ?
You might want to invest in a copy of Valgrind yourself sometime. I can get you a 10% off discount :-)
All of these new valgrind warnings that are products of my patches are a result of testing unimplemented features which will soon be implemented, so I'm not too worried about these. Besides, using valgrind is still a pita, and your patch makes it easier, but it keeps me from being able to 'commit -a'.
I don't like being able to do commit -a either, since valgrind errors are considered serious, should the patch be merged upstream?