Is there something like "Automatic crash information collection system" with ReactOS system?
When one program crash with freebsd system, it Automatically generated one file which clude many useful information.
When word.exe crash with windowsXP system, it automatically ask user to allow collecting some information to microsoft for Improving the software.
Maybe we can make a service into reactos which can automatic collect some useful information to developer.
Of course, its running should be allowed by user's mind.
You know, lot's of reactos's fans have no any Programming experience , even can not analysis which information be useful for developping.
But our fans have enthusiasm and confidence. we want to do someting for reactos system.
Forgive me so poor English.
Is there Automatic crash information collection system?
Moderator: Moderator Team
Re: Is there Automatic crash information collection system?
+1
Count me in, I'd LOVE to have that. If not automatic, then at least "user-startable" - e.g., you start this thing, and then it asks you to pick a program. When you have picked it, it asks you whether XY is really the program you wish observed. You can say yes or pick another one - but if you say yes, then it "observes" that chosen program and creates a file if that program crashes (or terminates otherwise)... or when you say that some information should be generated, even before a crash.
Best would be a neat little text file that you can e-mail or post somewhere.
This way, you can "observe" known "misbehaving" programs.
Maybe such a thing exists already, I just don't know... But this catching of serial output, as it exists now, is a mess; it might work, but it is not having too much of a future perspective.
Count me in, I'd LOVE to have that. If not automatic, then at least "user-startable" - e.g., you start this thing, and then it asks you to pick a program. When you have picked it, it asks you whether XY is really the program you wish observed. You can say yes or pick another one - but if you say yes, then it "observes" that chosen program and creates a file if that program crashes (or terminates otherwise)... or when you say that some information should be generated, even before a crash.
Best would be a neat little text file that you can e-mail or post somewhere.
This way, you can "observe" known "misbehaving" programs.
Maybe such a thing exists already, I just don't know... But this catching of serial output, as it exists now, is a mess; it might work, but it is not having too much of a future perspective.
Re: Is there Automatic crash information collection system?
It is one of the long-term objectives, as it would really help out with reporting bugs, but unfortunately its something we are now missing entirely. Perhaps a future GSOC project, or some kind of CFI?
-
- Posts: 176
- Joined: Wed Oct 05, 2011 7:32 am
Re: Is there Automatic crash information collection system?
I would assume that, right now, there are enough bugs they know about that it's not important.
Once they've taken care of all the huge bugs, and all the crashes they know about, they'll look into a crash reporter.
Until then, they just have too much to do.
Once they've taken care of all the huge bugs, and all the crashes they know about, they'll look into a crash reporter.
Until then, they just have too much to do.
Re: Is there Automatic crash information collection system?
Maybe it only automatic collect important information by our requirement.
It maybe only need to add a Screening function.
It maybe only need to add a Screening function.
-
- Posts: 28
- Joined: Mon Aug 16, 2010 2:45 pm
Re: Is there Automatic crash information collection system?
Is crashrpt running with ReactOS?
Or make it into ReactOS?
Or make it into ReactOS?
Re: Is there Automatic crash information collection system?
http://tortoisesvn.net/crashhandler.html
^ slightly more talk about the crashrpt and also about crash-server.com that TortoiseSVN uses nowadays
^ slightly more talk about the crashrpt and also about crash-server.com that TortoiseSVN uses nowadays
Re: Is there Automatic crash information collection system?
Note that most of these crash handlers are only useful for catching application level crashes. It is kind of hard for a logger application to do anything when the OS has halted and is sitting at a BSOD.
They also can't help much for application freezes or applications that "run" but do so incorrectly.
They also can't help much for application freezes or applications that "run" but do so incorrectly.
Who is online
Users browsing this forum: No registered users and 24 guests