"Daniel C. Sobral" <[EMAIL PROTECTED]> wrote: > OTOH, though, FreeBSD's malloc() is very unlikely to return an out > of memory error. Why is that? What happens if the process hits its resource limits? Cheers Jon -- \/ Jon Ribbens / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
- Re: Replacement for grep(1) (part 2) Jake Burkholder
- Re: Replacement for grep(1) (part 2) Jamie Howard
- Re: Replacement for grep(1) (part 2) Dag-Erling Smorgrav
- Re: Replacement for grep(1) (part 2) Dag-Erling Smorgrav
- Re: Replacement for grep(1) (part 2) Dag-Erling Smorgrav
- Re: Replacement for grep(1) (part 2) Dag-Erling Smorgrav
- Re: Replacement for grep(1) (part 2) Assar Westerlund
- Re: Replacement for grep(1) (part 2) Dag-Erling Smorgrav
- Re: Replacement for grep(1) (part 2) Assar Westerlund
- Re: Replacement for grep(1) (par... Daniel C. Sobral
- Re: Replacement for grep(1) (par... Jon Ribbens
- Re: Replacement for grep(1) (par... Daniel C. Sobral
- Re: Replacement for grep(1) (par... Jon Ribbens
- Re: Replacement for grep(1) (par... Daniel C. Sobral
- Re: Replacement for grep(1) (par... Jon Ribbens
- Re: Replacement for grep(1) (par... Sheldon Hearn
- Re: Replacement for grep(1) (par... Jon Ribbens
- Re: Replacement for grep(1) (par... Sheldon Hearn
- Re: Replacement for grep(1) (par... Daniel C. Sobral
- Re: Replacement for grep(1) (par... Jon Ribbens
- Re: Replacement for grep(1) (par... Daniel C. Sobral