Re: Setting memory allocators for library functions.

[Peter Seebach]

In message <[EMAIL PROTECTED]>, Julian Elischer writes:
>I still think that in such a case it should be possible to
>'test the commitment' by touching all the allocated memory 
>while trapping page faults.

And what do you do if you get one?  There's no undo button for SIGSEGV.
Traditionally, you return from the signal handler right where you were.
Can you get out of this with longjmp()?  Probably.  It's not exactly
supported or guaranteed.

In any event:

1.  The C language spec doesn't require you to do this.
2.  Other implementations have provided this guarantee, at least as an
option.

It's odd that I see lots of people arguing for segfaults killing the process
accessing memory that has been "successfully" allocated, but no one arguing
for the process getting killed when it exceeds a disk quota.

-s

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message