From: Scott L. <sc...@sw...> - 2005-06-09 16:31:00
|
Nicholas Nethercote wrote: > On Thu, 9 Jun 2005, Scott Long wrote: >> As I said in my original post, I don't think this is a problem. Pick >> one arbitrarily (to make it simple, just use the most recent). The >> developer will fix that error. Memcheck is run again, and now the next >> error is reported. In nearly all realistic cases, only a few >> uninitialized values will be involved. > > > It sounds to me like a good compromise. Patches are welcome! I'd love to, but it'll take me weeks to rummage through the code enough to understand the right way to do it. I'll come back to this the next time I have enough free time, but I will need some help identifying the proper places to make the changes. Please note that I am simply offering an idea, not making demands. There's too much of that crap going around... -- Scott Long <sc...@sw...> Software Engineer SwiftView, Inc. (971) 223-2639 |