> Crafting an exploit that does anything beyond crashing the program or the computer would require knowing how this was done for a particular program. No it do

> Crafting an exploit that does anything beyond crashing the program or the computer would require knowing how this was done for a particular program. No it doesn't. You can run your exploit code and then crash the program, same as exploiting any other program. Or you can add some minimal code on the end of your exploit payload to exit cleanly. If you really wanted to gold-plate it by having it resume the program where it had been then yes, you'd need to figure out some details, but that's not normal or necessary - classical "smash the stack" style exploiters rarely tried to unsmash the stack afterwards, they'd execute their payload and then exit or crash.