[chromium-dev] Re: Crash reporting and about:crash.

2009-06-16 Thread Stuart Morgan

On Tue, Jun 16, 2009 at 2:32 PM, Scott Hesssh...@chromium.org wrote:
 So, I'm inclined to mark it WontFix, except that then searches in the
 Issues database won't find it.

Do we think it's something people are actually likely to search for?
The crash aggregator will still have the bug number listed for that
stack, and that seems like the most likely (only?) place someone would
be inspired to look for a bug about it in the first place.

-Stuart

--~--~-~--~~~---~--~~
Chromium Developers mailing list: chromium-dev@googlegroups.com 
View archives, change email options, or unsubscribe: 
http://groups.google.com/group/chromium-dev
-~--~~~~--~~--~--~---



[chromium-dev] Re: Crash reporting and about:crash.

2009-06-16 Thread Scott Hess

On Tue, Jun 16, 2009 at 3:37 PM, Stuart Morganstuartmor...@chromium.org wrote:
 On Tue, Jun 16, 2009 at 2:32 PM, Scott Hesssh...@chromium.org wrote:
 So, I'm inclined to mark it WontFix, except that then searches in the
 Issues database won't find it.

 Do we think it's something people are actually likely to search for?
 The crash aggregator will still have the bug number listed for that
 stack, and that seems like the most likely (only?) place someone would
 be inspired to look for a bug about it in the first place.

Is the crash aggregator's annotation stable across releases?  If so,
then that makes sense.

I was assuming that if the fingerprint changes because we rearrange
the calling sequence somehow, then maybe someone has to re-annotate
things.

-scott

--~--~-~--~~~---~--~~
Chromium Developers mailing list: chromium-dev@googlegroups.com 
View archives, change email options, or unsubscribe: 
http://groups.google.com/group/chromium-dev
-~--~~~~--~~--~--~---