# Is a question that turns out to be a bug-report a valid question for SO?

If someone reports a problem, and others cannot find a mistake in the code, it may turn out to be a bug in the software used.

Basically, I was wondering if SO is a valid platform for apparent bug-reports and/or bug-investigations?

If not, how do we deal with these questions?

-
For example? This is a bit too vague... –  Oded Dec 13 '12 at 13:55
Do you expect the maintainers of the software to check Stack Overflow for bug reports? If no, then I wouldn't post it there. And even if so: What about a bug report is an actual question? –  slhck Dec 13 '12 at 13:57
@ʞɔɥls I don't know if maintainers do or do not follow their own tags on SO. I don't have a particular bug myself, it's just that I have come across such questions a few times. Oftentimes these questions start out as users asking for help with an error. Only if several people do not see a user-mistake it may turn out to be a bug. –  Jasper van den Bosch Dec 13 '12 at 14:03
PS with regard to the example: This question may definitely be of value to me and other mod_wsgi users, I am not trying to get rid of it, just trying to get a feel for this. –  Jasper van den Bosch Dec 13 '12 at 14:06
I see now. I understood "bug report" as an actual reporting of the bug in the question. If you ask a valid question and it turns out to be a bug, so be it, but that should of course be in the answer (or the question could be closed as too localized if that bug makes the problem unsolvable). –  slhck Dec 13 '12 at 14:08
Furthermore, if you can figure out a workaround, you can post it as an answer. Here's an example that recently happened to me: stackoverflow.com/q/13804194/1015495 –  mikeTheLiar Dec 13 '12 at 15:11

It's a bug in line 42 of foo.lang, where they use > instead of >=. I've filed a bug report at http://thebugtracker.example.com/issue/42 and a workaround is to frobnicate the baz before calling foo.