Kerb to Programmer [email protected] • 2 years agoways to close vimdiscuss.tchncs.deimagemessage-square42fedilinkarrow-up1228arrow-down122
arrow-up1206arrow-down1imageways to close vimdiscuss.tchncs.deKerb to Programmer [email protected] • 2 years agomessage-square42fedilink
minus-square@[email protected]linkfedilink18•2 years agocat /dev/zero > "/proc/$(pidof vim)/mem" is my favorite dumb way. Clear its memory, wait for the segfault.
minus-squareJulianlinkfedilink2•2 years ago…you can write to program memory? Idk how exactly but that feels like a security risk.
minus-square@[email protected]linkfedilink6•2 years agoIt’s your process, why shouldn’t you be able to write to it? Vi is certainly doing it…
minus-square@[email protected]linkfedilink5•2 years agoYou do need to be root to do it to arbitrary processes.
minus-square@[email protected]linkfedilink1•edit-21 year ago dumb way. Get fancy, add progress bar: pv < /dev/zero > “/proc/$(pidof vim)/mem”
cat /dev/zero > "/proc/$(pidof vim)/mem"is my favorite dumb way. Clear its memory, wait for the segfault.…you can write to program memory? Idk how exactly but that feels like a security risk.
It’s your process, why shouldn’t you be able to write to it? Vi is certainly doing it…
You do need to be root to do it to arbitrary processes.
Get fancy, add progress bar: pv < /dev/zero > “/proc/$(pidof vim)/mem”