Before reporting a bug, it's usually a good idea to check the FAQ and this forum to see if anyone else has already encountered something similar.

If you are unsure whether or not something is a bug, you can always create a thread in this forum to discuss it.

If the problem indeed seems to be a genuine bug, the best way to get developer attention is to post detailed information about it in the Spring bugtracker. We have recently switched over to the Mantis bugtracker, and it can be found here.

Read this to increase chances of your bug fixed:

http://www.chiark.greenend.org.uk/~sgtatham/bugs.html

When reporting a crashbug always include:

Operating system e.g.(Ubuntu/redhat/Windows XP/Vista/etc)
Serice Packs/versions e.g.(XPSp1a/2000 sp3/Ubuntu 6/Ubuntu 7/etc)
Graphics card e.g.(nvidia GF 6600/ATI 9900/etc)
cpu e.g.(AMD duron 1.4Ghz/Intel core 2 duo e6600 2.5Ghz)
ram e.g.(2GB DDR2/512MB SDRAM/etc)

Does that include logic bugs like e.g. arced missiles not hitting targets at different heights?

And, possibly 10x more important, include extact and detailed instructions on how to reproduce the bug.

If you do not / incorrectly describe the steps to reproduce it or it is not reproducable at all, chances of it ever being fixed are much smaller then if you do.

Don't just throw stacktraces at us and assume we can figure out how to reproduce them and what the context was by creating a telepathic link to your brain.

A how-to should contain information "how to" exactly report a bug, not just a link to a single page. I followed this link and there is no "submit bugreport here" button or something similar. So if it's your first time, you might stand confused and turn away. Why not also include information on whether it's useful or not to submit the infolog.txt within the bugreport or whether a single infolog could still help or not.

how abit someone editing the first post in the topic with a big fat link to mantis?

No if it's a big link people won't read the post before it.

I hope I perceive this being ignorance is wrong.
And a bigger link won't help, since there is already "bug tracker" in the main menu. The problem is how to use it. Since it appears you need to be "logged in" to submit a bug - if not, there's no button for it. Anyway, it lacks explanation, and it's not a "How-To", that is my point.

My best ways to get a bug fixed thread should have been stickied...

Time for time game crash and dump some info in infolog.txt May be it is good to post this logs somewhere? Or this information is not important?

upload the infolog.txt to http://pastebin.com,
then make a thread in this forum or a bug report on mantis:
http://springrts.com/mantis/
with the pastebin link attached.
give as much information as you can, eg:
"it happens at the start of the game, but only sometimes"
or
"it happens when i try to capture a unit from an AI team"
... you get it

Locked topic, the topic title is "How to report bugs", not "Report bugs here"