Re: How important is it to free() on run once programs?
This is a discussion on Re: How important is it to free() on run once programs? within the mailing.openbsd.tech forums, part of the OpenBSD category; --> > Theo de Raadt wrote: > > Doing free() before exit() is bad style. > > > > It ...
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
02-18-2008, 08:01 AM
| ||||
| ||||
 Re: How important is it to free() on run once programs? > Theo de Raadt wrote: > > Doing free() before exit() is bad style. > > > > It is not needed. > > > > But what I find more amusing is that on some system malloc's > > such things trigger exploitability of previous heap damage. > > It's mighty confusing indeed. > > But exit(3) does not mention that exit() also frees up the memory, > if I understood Claudio right. Would it be nice to add it the > manpage? No, no, no, it will *NOT* be added to the manual page! It terminates the bloody process! You seem to be seriously confused.      |
Linear Mode
