Kerb@discuss.tchncs.de to Programmer Humor@programming.dev · 1 year agoways to close vimdiscuss.tchncs.deimagemessage-square24fedilinkarrow-up1184arrow-down121
arrow-up1163arrow-down1imageways to close vimdiscuss.tchncs.deKerb@discuss.tchncs.de to Programmer Humor@programming.dev · 1 year agomessage-square24fedilink
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-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.
Get fancy, add progress bar: pv < /dev/zero > “/proc/$(pidof vim)/mem”