I was wrong in one of my earlier comments when I responded that it might be a while before we had public access to crash data. It looks like Jay's been working overtime to get a public look-up tool set up and today that work is sufficiently completed to make available to our testing and bug triage community.
The new tool is located at http://talkback-public.mozilla.org. From this page you can look up individual talkback reports . The reports contain the stack signature, product and build IDs, the time of the crash, the platform and OS, the code module, the user-entered URL and user comments, the trigger reason, trigger line number, and stack trace for the crash.
The stack lines in the stack trace are each linked to a bugzilla query for existing bug reports with that class and function in the comments. This makes it easy to discover if your crasher is already reported. Just look up your talkback ID, click the top line of the stack trace and have a look at the resulting bug list to see if one of those reports matches your crasher.
In addition to the individual incident ID look-ups, you can also look up our talkback "smart analysis" reports from that same page (1.7b example). These reports give some aggregate information and include our current list of topcrashes.
With the good news of this long-awaited triage tool comes some bad news that we lost a large number of previous crash reports because of some database problems we were having. So if you go to look up your incident from a week or two ago and don't get a report, that's the reason.
