When you need help for a stack trace, just copy the text of the stack trace and paste it to Samebug. However, please be careful and copy the full text of the stack trace, and include every character from the beginning of the exception type until the very end of the last 'Caused by' clause if there is any. A few missing characters can dramatically change the meaning of the stack trace and Samebug has no means to recognize if you made a mistake or did that on purpose.
To save you from this hassle we created the Samebug plugin for IntelliJ Idea, Android Studio and Eclipse, which integrates Samebug with your development workflow by bringing stack trace search to right where you need it, one click away in the console of your IDE.
If you paste an arbitrary text into the search area of Samebug which can't be parsed as a valid stack trace, Samebug will fall back to text search mode. In many cases this might be still good enough for you, but using stack trace search will always produce more relevant results. Only when you paste a valid stack trace, can Samebug analyze the semantics of the stack trace and use our unique stack trace similarity algorithm.
This is the result page when you search with the first line of a StringIndexOutOfBoundsException. As you can see, the first tip is silly, only the second is relevant. Also, there are more than ten thousand external solutions (most of them are probably not that helpful), and Samebug cannot connect you to bugmates.
However, when you search with the full stack trace of a StringIndexOutOfBoundsException, Samebug gives you this: