In general I love stacktraces. Most of them I cause by raising my own exception :)
What I hate is, when my app ran into a state where it obviously stopped working, but I don't get a stacktrace.
I currently work on a game that is being tested as a closed beta with 2500 players. When it crashes, we get sent a stacktrace, a screenshot and a server protocol and we can usually fix the problem within hours.
Of course I generally try to provoke stacktraces in my tests. Now if you get plenty of crashes in a product that you deliver, then that's definitely a problem, because your tests should have triggered them already.
I think you can hardly deliver a reliable product without hallway testing (except if you're into software verification and have a lot of money to spend). And if stacktraces show up before or during that phase, well that's excellent. If they show up after that, you did your job wrong.