Re: [Valgrind-users] Memcheck's uninitialised value errors...

[Nicholas N. <nj...@cs...>]

On Mon, 15 Dec 2008 eyu...@ab... wrote:

> Lets say that all of the difficulties we discussed until now have been
> resolved. Is there any other reason for valgrind not to do eager
> checking for this?

A big slow-down -- instead of having to check memory accesses, syscalls, 
conditional branches, and a few other places for undefined values, it would 
have to check just about every instruction.

Nick