Let's say a (very) large process is crashing and dumping core, and we know the cause from other information (possibly an assert message, maybe something else).
Is there a way to stop the core dump from being completely generated, since it's a waste in this case?
For instance, would kill -9 of a core dumping process interrupt the corefile generation?
Obviously, if we knew ahead of time that we don't want core dumps, we could set the ulimit appropriately or use the OS's various core file control utilities.
But this question is about the "core dump already in progress" stage...
(For instance, imagine I'm the requestor in http://stackoverflow.com/questions/18368242/how-to-bypass-a-2tb-core-dump-file-system-limit and don't want to waste 5-6 TB of disk space :) )