[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Óscar Fuentes
Subject: Re: [Emacs-diffs] master 6cd5678: Clarify compiler-pacifier in frame.c
Date: Mon, 26 Aug 2019 17:21:37 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux)

Eli Zaretskii <address@hidden> writes:

>> For these tools it is helpful to say that a variable is not
>> initialized, because that helps catch use-before-set errors. An
>> explicit initialization would cause these use-before-set bugs to go
>> uncaught by these debugging tools.
> 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.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]