Maybe it's "stupid parser error debugging", where a single missing comma in a csv, or a missing semi-colon in a long one-line shell script, causes a bizarre, misleading error message.
Something where your tools mislead you because the input broke all the assumptions that were made.
In my experience I then have to resort some quick slice-and-dice work in a text editor to bisect the problem, and I'll eventually find it, but it is tedious and not fun. And your reward is usually learning "the input was wrong", not "the code is wrong".
Something where your tools mislead you because the input broke all the assumptions that were made.
In my experience I then have to resort some quick slice-and-dice work in a text editor to bisect the problem, and I'll eventually find it, but it is tedious and not fun. And your reward is usually learning "the input was wrong", not "the code is wrong".