|
From: smiley g. <smi...@ya...> - 2006-02-07 09:46:56
|
Hello, An Uninitialized variable used in many places makes memcheck print an error for each location of the read. With a complex application with many errors this becomes too cumbersome as I end up having 2 or more different stack traces for the same source variable (same problem). Is there a way by which I can set the variable as defined after firing the first error for uninitialized read. This way I have the first read thats usually closest to the source of the error. Thanks, Smile. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |