A signal handler is not guaranteed to work. It must be written such that it does not require a new page of memory. Some possible problems here are the stack growing, writing on a new page in the data segment, etc. I'm not familiar enough with the VM system, but if you couldn't create a new swap page for a process, what would guarantee that the signal handler could get the pages it needs.
Jim Bloom bl...@acm.org Mikhail Teterin wrote: > > If we are up to discussing the possible implementations, I'd suggest > that the system uses something other then SIGKILL to notify the > program it's time to pay for the over-commit speed and convenience. > I think, SIGBUS is appropriate, but I'm not sure. > > Anything a program can _catch_ and react upon, if its author chooses > to. > To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
