Time to abandon stack as a 'display'? That's why they overflow (mostly) - lots of large items or lots of recursion and local variables. Also having the address

Time to abandon stack as a 'display'? That's why they overflow (mostly) - lots of large items or lots of recursion and local variables. Also having the addressable method arguments in the same space as the return address, allows a whole host of other bugs and cracks. I have long thought, the return stack should be a memory region un-addressable by the code except via call and return. Local method arguments could then revert to ordinary allocations or some other check-able allocation, and have normal error recovery.