On Wed, Apr 22, 2009 at 05:40:28PM -0000, Steve Beattie wrote:
> Being able to correlate when a crash occurs with other event in logfiles
> is usually pretty important. In the bug I linked to, the person
> attempting to diagnose the issue had a hypothesis that the bug had
> occurred during an upgrade and not after the reboot; however, the only
> way to verify when the crash actually occurred was to look at the date
> stamp on the crashfile itself to confirm or deny that hypothesis.
>
> I share your concern with not overwhelming triagers with all the
> information available when a bug is reported; perhaps the dropped
> information could be combined into a separate attachment (e.g.
> CrashDetails) so that it doesn't clutter the bug's description but is
> available should it be necessary for diagnosing the bug?
I assume Martin subscribed me because the suggestion to remove it came from
me (I don't quite recall). FWIW, I have no objection restoring it if it's
useful.
On Wed, Apr 22, 2009 at 05:40:28PM -0000, Steve Beattie wrote:
> Being able to correlate when a crash occurs with other event in logfiles
> is usually pretty important. In the bug I linked to, the person
> attempting to diagnose the issue had a hypothesis that the bug had
> occurred during an upgrade and not after the reboot; however, the only
> way to verify when the crash actually occurred was to look at the date
> stamp on the crashfile itself to confirm or deny that hypothesis.
>
> I share your concern with not overwhelming triagers with all the
> information available when a bug is reported; perhaps the dropped
> information could be combined into a separate attachment (e.g.
> CrashDetails) so that it doesn't clutter the bug's description but is
> available should it be necessary for diagnosing the bug?
I assume Martin subscribed me because the suggestion to remove it came from
me (I don't quite recall). FWIW, I have no objection restoring it if it's
useful.
--
- mdz