Re: [Emacs-diffs] master 6cd5678: Clarify compiler-pacifier in frame.c

[Eli Zaretskii]

> > What debugging tools can make a significant difference here, and how
> > easy/practical is it to use them?  I very much doubt they will catch
> > every use-before-set bug anyway.
> 
> Valgrind tracks each byte at the machine instruction level.
> 
> Given the complexity of the Emacs C code, IMAO it is very useful to test
> for this type of nasty errors. I dislike hacks that pollute the source
> code, but on this case it is warranted.

Does valgrind know about UNINIT?  I'd be surprised, since UNINIT is a
source-level feature.