should have added the report where we correlate bug numbers
and top crash info using the summary field information for those
that are interested... It is here...
ftp://ftp.mozilla.org/pub/data/crash-data/seamonkey-crash-analysis.txt
chris h.
chris hofmann wrote:
[EMAIL PROTECTED]">
Andreas Franke wrote:
[EMAIL PROTECTED]">way nice...Gervase Markham wrote:http://bugzilla.mozilla.org/duplicates.cgi .
Nice. :)
[EMAIL PROTECTED]">2) We need to do better summaries.
The only description people get of bugs is the Summary. In the past, I
sometimes invent new summaries for the mostfreq list if the summary is
something like "Crash in Trunk [@ nsWalletlibService::OnStateChange]".
However, this will no longer be possible, so summaries need to describe
symptoms, and the fact that the crash is in OnStateChange can safely be
left in a comment. [...]
I disagree. Having the top of the crashing stack in the summary is the only
way to quickly find out if a new crasher is a dupe or not. The topcrash
tracking effort also uses this, so if the summary is not the right place for
this, we need to find a substitute, and use it consistently. The only easily
searchable alternative text field that doesn't need changes to bugzilla
(which won't happen anytime soon because bugzilla only accepts "security"
fixes till the 2.14 release) is the status whiteboard field.
In the long run, I think an editable "long summary" field would be nice to
have. See e.g. my 2001-02-19 23:38 comment in bug 540.
Yes, the particular [@ nsTopothe::Stack] syntax is used by the [EMAIL PROTECTED] to
generate reports that help us to make sure bugs are filed for all the top crashers. Please
don't monkey with this unless you want to add another field that we can easily search that
has top of stack info.
thanks
chris h.
[EMAIL PROTECTED]">
Andreas
