'CRASH LOG FILE's — will shedding light on crashes

Hi guys :) I think it will give more effective way to give developers more clear informations when blenders crash/fall. Mainly for this moments. For example I found that I have had about 20-30 crashes (from moment when I start usiing blender) and I even din't know what was happend then so can't even tell about it. But that was 'hard' bugs...that closed software. And current situation lead to give feedback only/dominately about 'soft' things/bugs that you clearly understand how they works and how they corrupt blender. But at first, it will happends really rarely and at second it usual will be minor bugs [That oposite - not will crush blender]. While real crasshes that will happends and need fix at first time, but because anyone don't know "what the hell was happend just right now" ... will have long way before someone will understood it nature and report about it. And that lead all system to priority upside down - when soft bugs will fixed at first and hard at last.

So I propose something like folder where blender will save his LOG file. And then after each crashes user can attach this[last] file and give his small last few steps description. And it allow devs more clearly undersand waht happend. And it will allow users give feedback even they don't know what was the reason of it. Anothe side of coin is that sometimes you even know how to reproduce bug, but you need necessarily to attach file (but you can't do it for some reason.. for example by NDA or any others) and just haven't any time(in current moment) to capture this bug from scratch whith default settings and tell about it. But then you will forget about it.

About Log-file.. maybe it will work like History racording users actions, or maybe like sectors markers, I think develepors guys more competent in this area.

But here is dark side too: it will lead to multiply reports too..