Tom Spear wrote:
Just curious to see if anything was ever done with the offer to upgrade bugzilla?
On a side note, it would be nice if there was a crash keyword to make finding crashes easier
Searching for "Unhandled exception" is too hard?
On 5/22/07, Robert Shearman rob@codeweavers.com wrote:
Searching for "Unhandled exception" is too hard?
Not all bugs have a proper trace, not all crashes result in the unhandled exception message (100% cpu usage being one case), not all bugs say crash (some say hang, or stuck, 100% cpu usage, freeze, etc). So If we had a crash keyword, then as people look at the new bugs, it can be added. Then people who are looking for crashes to fix or at least debug further (as I do), can find those bugs easier.
On 5/22/07, Tom Spear speeddymon@gmail.com wrote:
On 5/22/07, Robert Shearman rob@codeweavers.com wrote:
Searching for "Unhandled exception" is too hard?
Not all bugs have a proper trace, not all crashes result in the unhandled exception message (100% cpu usage being one case), not all bugs say crash (some say hang, or stuck, 100% cpu usage, freeze, etc). So If we had a crash keyword, then as people look at the new bugs, it can be added. Then people who are looking for crashes to fix or at least debug further (as I do), can find those bugs easier.
I don't see how a 'crash' keyword will add any utility to bugzilla. Is someone planning on focusing solely on apps that crash, and if so, why?
On 5/22/07, James Hawkins truiken@gmail.com wrote:
I don't see how a 'crash' keyword will add any utility to bugzilla. Is someone planning on focusing solely on apps that crash, and if so, why?
Well, when I look thru bugzilla, that is my main focus is find bugs with crashes, and try to debug them as far as I can so that all the info is there to write a fix without a real developer having to sit there and hold a user's hands thru the dirty part.
I'll ask what the progress is with our Bugzilla upgrade when the one who offered this comes online again.
On Tue, May 22, 2007 at 03:25:40PM -0500, Tom Spear wrote:
On 5/22/07, Robert Shearman rob@codeweavers.com wrote:
Searching for "Unhandled exception" is too hard?
Not all bugs have a proper trace, not all crashes result in the unhandled exception message (100% cpu usage being one case), not all bugs say crash (some say hang, or stuck, 100% cpu usage, freeze, etc). So If we had a crash keyword, then as people look at the new bugs, it can be added. Then people who are looking for crashes to fix or at least debug further (as I do), can find those bugs easier.
I would consider neither of hang, stuck, 100% cpu usage, freeze to be a crash.
I think that regardless of the result of the bug it might be useful to check that it gets debugged.
So we might distinguish two boolean variables for bugs: - (1) Has it all the information that can be provided (e.g. crash log and back-trace with debug symbols)? This would also contain checking that all the fields are properly set. - (2) Do we know the cause for the bug? ( E.g. for a segmentation fault AKA crash in the application, do we know what in Wine caused it? )
Should we include in (1) if it can be reproduced independently?
Jan
On 5/22/07, Jan Zerebecki jan.wine@zerebecki.de wrote:
I'll ask what the progress is with our Bugzilla upgrade when the one who offered this comes online again.
Thanks
I would consider neither of hang, stuck, 100% cpu usage, freeze to be a crash.
Out of curiosity, why not?
I think that regardless of the result of the bug it might be useful to check that it gets debugged.
So we might distinguish two boolean variables for bugs:
- (1) Has it all the information that can be provided (e.g. crash log and back-trace with debug symbols)? This would also contain checking that all the fields are properly set.
- (2) Do we know the cause for the bug? ( E.g. for a segmentation fault AKA crash in the application, do we know what in Wine caused it? )
Should we include in (1) if it can be reproduced independently?
That would be helpful to you guys, so I see no problem with it.
On Wed, May 23, 2007 at 09:01:17AM -0500, Tom Spear wrote:
On 5/22/07, Jan Zerebecki jan.wine@zerebecki.de wrote:
I would consider neither of hang, stuck, 100% cpu usage, freeze to be a crash.
Out of curiosity, why not?
It's probably the narrow definition from the POV of someone who thinks of how a crash comes to be. An application crashes when it receives a unhandled or unexpected exception, otherwise the application is still running or it exited (without crashing).
Anyway we agree that ideally every report should get checked by someone.
Jan
On Wed, 2007-05-23 at 04:36 +0200, Jan Zerebecki wrote:
I'll ask what the progress is with our Bugzilla upgrade when the one who offered this comes online again.
While you are asking, make sure they are going to Bugzilla 3.0. Since that just went stable not very long ago.
I may make a suggestion for upgrading. It may be easier to start a new DB for Bugzilla, and write a script that imports all the old data to the new tables.
On 5/23/07, Jeremy Newman jnewman@codeweavers.com wrote:
On Wed, 2007-05-23 at 04:36 +0200, Jan Zerebecki wrote:
I'll ask what the progress is with our Bugzilla upgrade when the one who offered this comes online again.
While you are asking, make sure they are going to Bugzilla 3.0. Since that just went stable not very long ago.
I may make a suggestion for upgrading. It may be easier to start a new DB for Bugzilla, and write a script that imports all the old data to the new tables.
I think I would even prefer that.. Maybe it could be set to not import anything that had the abandoned or invalid flags so that we have a leaner meaner db as well?
-
James Hawkins -
Jan Zerebecki -
Jeremy Newman -
Robert Shearman -
Tom Spear