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.