The result is completely unpredictable and it may "just" crash indeed, but I've also seen it trigger silent infinite loops if the invalid stack frames are bad enough, or the segv_handler can handle the crash and restore the thread to another corrupted frame, again and again. This can and does end up with stuck processes.
Wait, why aren't we sending processes SIGKILL in that case? If we need to kill the process we should be sending SIGKILL anyway; there's no guarantee it'll respond to SIGQUIT in the first place.