Re:Show HN: I wrote a Java decompiler in pure C language
by guerrilla on Tuesday June 03, 2025 @05:00PM
(#44174670)
Pretty sure you can just disable leak checking.
[ Parent
| on HN ]
Re:Show HN: I wrote a Java decompiler in pure C language
by 1718627440 on Tuesday June 03, 2025 @05:04PM
(#44174721)
But for example verifying that memory is not touched after it is supposed to, is much harder when you can't rely on it being freed.
Of course literally running valgrind is still possible, but it is difficult to get useful information.
Re:Show HN: I wrote a Java decompiler in pure C language
by nick__m on Tuesday June 03, 2025 @05:40PM
(#44175037)
You cannot have use-after-free if you never call free, so there are no points at which memory should not be touched.
That's the beauty of the never free memory management strategy.