Good idea! I would just have a few suggestions to make it even more useful: - "Consider filing a ticket at https://jira.reactos.org/ if it wasn't already reported there. To do so, provide information on what..."
- "Ideally, try to reproduce the problem while capturing a debug log that you should translate afterwards. See https://"; Cheers, Pierre Le 11/01/2018 à 00:48, Thomas Faber a écrit : > We often get bug reports with just a screenshot of a bluescreen; we then > go ahead and tell people that bluescreens are basically useless, they > should get a debug log and a backtrace, and also remember to tell us > what version they're using. > > Since there's actually no reason why bluescreens need to be useless, I > thought I'd try to change that. > I've attached an example. The source for this quick PoC can be found at > https://github.com/ThFabba/reactos/commit/6a9f172b76bd11f763598c16e5d47299eec1971c > > Thoughts? > > > > _______________________________________________ > Ros-dev mailing list > Ros-dev@reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev > -- Pierre Schweitzer <pierre at reactos.org> System & Network Administrator Senior Kernel Developer ReactOS Deutschland e.V.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
