Dag-Erling Smorgrav scribbled this message on Jul 20: > When I allocate memory, I usually intend to put something in it. > There's always the odd struct sockaddr_in which I bzero() before > filling it in, but they're usually on the stack. and even then, I don't believe in filling sockaddr_in w/ bzero, I believe in using getsockaddr on it so that you actually get all the fields filled out properly... -- John-Mark Gurney Voice: +1 541 684 8449 Cu Networking P.O. Box 5693, 97405 "The soul contains in itself the event that shall presently befall it. The event is only the actualizing of its thought." -- Ralph Waldo Emerson To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
- Overcommit and calloc() Kelly Yancey
- Re: Overcommit and calloc() Dag-Erling Smorgrav
- RE: Overcommit and calloc() Kelly Yancey
- Re: Overcommit and calloc() Dag-Erling Smorgrav
- Re: Overcommit and calloc() Dan Nelson
- RE: Overcommit and calloc() Kelly Yancey
- RE: Overcommit and calloc() Kelly Yancey
- Re: Overcommit and calloc() Dag-Erling Smorgrav
- Re: Overcommit and calloc(... John-Mark Gurney
- Re: Overcommit and cal... Dag-Erling Smorgrav
- Re: Overcommit and calloc() Ville-Pertti Keinonen
- Re: Overcommit and calloc() Peter Dufault
- RE: Overcommit and calloc() Charles Randall
- Re: RE: Overcommit and calloc() Matthew Dillon
- RE: Overcommit and calloc() Kelly Yancey
- RE: Overcommit and calloc() David Wolfskill
- RE: Overcommit and calloc() Bob Bishop
- Re: RE: Overcommit and calloc() Matthew Dillon
- Re: RE: Overcommit and calloc() Bob Bishop