owl@beach.city wrote:
(In this case it wasn't a C issue, but I bring it up because it seems incredibly irresponsible. The issue would have manifested in the same way in C♯ or other memory-safe languages.)