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; --> On Sat, Aug 27, 2005 at 11:43:01AM +0200, Han Boetes wrote: > Theo de Raadt wrote: > > Doing ...
| |||||||
| 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? On Sat, Aug 27, 2005 at 11:43:01AM +0200, Han Boetes wrote: > 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? > Exit terminates a process. If a process is terminated there is no memory left to free. The kernel removes all memory mappings and so all allocated memory is gone. exit(3) does not cleanup malloced memory. -- :wq Claudio      |
 |
« Re: How important is it to free() on run once programs?
|
Re: How important is it to free() on run once programs? »
| Thread Tools | |
| Display Modes | |
Linear Mode
|
|
All times are GMT. The time now is 11:31 PM.
