News for hackers. Stuff that matters.

A comment on Podman: A Daemonless Container Engine. Parent comment

Re:Podman: A Daemonless Container Engine by CivBase on Thursday February 11, 2021 @02:12PM (#26105802)
Are you saying that every project written in C has suffered from a memory leak issue at some point? Most C/C++ code I've personally written doesn't even use the heap.

I work on avionics and we use C/C++ now and then. We have a ton of rules regarding memory management (pretty much everything stays on the stack) and I can't recall anything I've ever been involved with suffering from a memory leak.

[ Parent | on HN ]
Re:Podman: A Daemonless Container Engine by Cyph0n on Thursday February 11, 2021 @11:04PM (#26110625)
If basically everything stays on the stack, you’ll have a much lower chance of seeing a memory leak, by definition.
[ Parent | on HN ]
Re:Podman: A Daemonless Container Engine by CivBase on Friday February 12, 2021 @01:28PM (#26116809)
Exactly. Using C/C++ doesn't have to mean using the heap.
[ Parent | on HN ]
Re:Podman: A Daemonless Container Engine by eptcyka on Saturday February 13, 2021 @04:16AM (#26122457)
Using the heap has nothing to do with the code being safe or unsafe.
[ Parent | on HN ]
Re:Podman: A Daemonless Container Engine by tshtf on Thursday February 11, 2021 @02:14PM (#26105822)
All I'm saying is that it's a trivial oversimplification to say you can learn to miss every time.
[ Parent | on HN ]
Re:Podman: A Daemonless Container Engine by eptcyka on Saturday February 13, 2021 @04:15AM (#26122454)
Don't need a leak for C code to be vulnerable, in fact not using the heap helps - just one missing bounds check on user input and you can write to the stack. OTOH, W^X should catch those.
[ Parent | on HN ]