Messages in this thread | | | Date | Mon, 19 Jan 1998 23:49:01 +0100 (CET) | From | MOLNAR Ingo <> | Subject | Re: 3.0 wishlist Was: Overview of 2.2.x goals? |
| |
On Mon, 19 Jan 1998, Dan Hollis wrote:
> Quite often (50% - 60%) of the time, there is not enough information from > an OOPS to know what happened. Ive got a huge pile of oops reports where > all anyone could do is shrug their shoulders and say 'well, if it happens > again let me know. i dont have the slightest clue because theres not > enough information from an OOPS to tell.'
an OOPS 100% tells you where and why the oops happened. Now, to determine what the real reason for the oops was is quite complex, and in many cases a crashdump doesnt help much. I would say the existance of a crashdump hinders development more than the nonexistance of it ...
[btw., is that pile of symbolic oopses accessible somewhere?]
-- mingo
| |