I've reached my limit of the number of "please read my stack trace to me" questions posted on SO. It's essentially like someone wanting you to read to them. I keep answering politely, but there must be a better way to teach users how to read their own stack trace.
"Here is a book that tells me exactly what line of code produced the error, will you read it to me?"
I understand that we all have to start somewhere, and I believe that somewhere should be learning how to read a stack trace.
My proposal or feature request is a linkable item like
[answer] that takes the user to a helpful page (FAQ page possibly) that gives directions on how to read a blasted stack trace. It can be inserted into comments (and I think in answers). Something like
[stacktrace] would be appropriate. Being that this is a programming Q&A site, I feel that this would be an essential addition to the SO tool belt.
This will also show the user how to deal with exceptions before asking on SO. Instead of entering into "OMG Look at all this text, I can't understand this jibberish, let me go post this error log on StackOverflow!" mode everytime they see a stack trace, they can instead say "Great, the error is at line 120 of Main.java, lets debug."
I read FAQ for Stack Exchange sites and was not sure if I should propose this as a FAQ, or a feature request, or what. I'm an active member on SO, but this is my first post on Meta.
If this has already been requested, or done, then please close my question. I did search first and found Stack trace wiki on SO but it was a little different than what I am asking.