Kerb@discuss.tchncs.de to Programmer Humor@programming.dev · 1 year agoways to close vimdiscuss.tchncs.deimagemessage-square42fedilinkarrow-up1230
arrow-up1230imageways to close vimdiscuss.tchncs.deKerb@discuss.tchncs.de to Programmer Humor@programming.dev · 1 year agomessage-square42fedilink
minus-squareEufalconimorph@discuss.tchncs.delinkfedilinkarrow-up18·1 year agocat /dev/zero > "/proc/$(pidof vim)/mem" is my favorite dumb way. Clear its memory, wait for the segfault.
minus-squareJulian@lemm.eelinkfedilinkarrow-up2·1 year ago…you can write to program memory? Idk how exactly but that feels like a security risk.
minus-squarenintendiator@feddit.cllinkfedilinkarrow-up6·1 year agoIt’s your process, why shouldn’t you be able to write to it? Vi is certainly doing it…
minus-squareEufalconimorph@discuss.tchncs.delinkfedilinkarrow-up5·1 year agoYou do need to be root to do it to arbitrary processes.
minus-squarevrkr@programming.devlinkfedilinkarrow-up1·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”