3 ms·
Would this be the case if you just used the `free(3)` syscall, and didn't otherwise touch the memory? I can imagine destructors in most languages involving tou
by slimsag 5y ago
Would this be the case if you just used the `free(3)` syscall, and didn't otherwise touch the memory?
I can imagine destructors in most languages involving touching the memory, just curious if a free syscall alone does it or not.
- astrange 5y agoAbove 16KB (one page) it's safer. Depends how much work you need to do to figure out what can be freed. It's better to free things as you go rather than wait for warnings.
- namibj 5y agoSection 3 are library calls, section 2 has the actual syscalls.
- matvore 5y agoSome related trivia. The `errno` command, for looking up syscall error codes, is not installed in `/usr/bin` in macOS like on typical Linux distros. But the same information is available in `intro(2)`, e.g. $ man 2 intro | grep -w 17 17 EEXIST File exists. An existing file was mentioned in an inappropriate