SOLVED Re: Memory leak in hush with NOMMU busybox-1.37.0

Mon Aug 4 11:15:41 UTC 2025

On Mon, 4 Aug 2025 at 13:11, Denys Vlasenko <vda.linux at googlemail.com> wrote:

> The correct fix is to specify the pointer in question as "volatile"
> variable, so that gcc stops making assumptions about its liveness.

You are right as a manual, Denis.

...but god knows what gcc does with a volatile which is not associated
with a hardware I/O line. (LOL)

However, from a PoV of least-change and least-footprint, volatile wins
as work-around. So volatile be!

Best regards, R-