While I think of myself as above this error, I can absolutely see myself falling for it. Messing with symlinks to dynamic libraries isn't uncommon and in the heat of a debugging session, the fact that I mess with the linker itself can go unnoticed. Of-course I would move it to a backup, but when accidentally also closing the last shell instance the problem amounts to the same.
Also the LLM output is so noisy, there are tons of shell commands, commands and a lot of useless text, which can easily make you miss the needle in the haystack what you are actually doing.
Sure sure, but really, if it found data about debugging really low level stuff and removing the linker is necessary to help narrow down the problem... it is just making use of its context. This is why jobs will only be going away on the dumbest of projects
Also the LLM output is so noisy, there are tons of shell commands, commands and a lot of useless text, which can easily make you miss the needle in the haystack what you are actually doing.