Main problems with debugging questions are:
- They usually need a talk to narrow down the problem
- They're likely to become Chameleon Questions where solving first problem surface another and doesn't solve the problem in OP's point of view, who edit it and change it enough to invalidate existing answer, turning into a forum like talk.
- There's chances the problem is not where the OP think it is, it's often a XY problem
While as in the case above there can be a 'kind of useful' answer, the answer itself has no real link with the question tittle and finding the root cause of the problem is not always easy.
Main problem could be that the OP will spot something wrong absolutely sideway of the question and as such no satisfying answer could be made, I'd argue my answer to the question above is not really satisfying or good, it just summarize what the OP found during the chat session.
We're not overwhelmed by the number of question for now, so my take would be to try to get them in an useful form if an answer can be made, if not, we should close it with (Started another meta for custom close reasons):
"This question was caused by a problem that can no longer be
reproduced or a simple typographical error. While similar questions
may be on-topic here, this one was resolved in a manner unlikely to
help future readers."
This assume there's people here willing to do 'interactive support', if there's no one for that, the question will stay as is if it's clear enough. If the OP is not responsive then it should be closed as Unclear".
