Let's just start with the basic idea, a bsod with a stacktrace.
Then, we can add onto that, maybe a qr code, or translate the addresses
etc..
On 13-1-2018 12:24, Hermès BÉLUSCA - MAÏTO wrote:
I suppose the idea of putting an idiotic smiley was the "idea" of an
intern ^^
Also our qr code would be actually useful, instead of the hardcoded
ones win10 seems to display (as it looks the idea of thomas would
include the backtrace in it).
H.
____________________
De : David Quintana (gigaherz)
Date : 13 janvier 2018 11h17
À : ros-dev@reactos.org
Cc :
Objet : Re: [ros-dev] Making bluescreens more useful
Whatever we do, DO NOT put a smiley in it. It feels like an insult.
On 13 January 2018 at 10:36, Ged Murphy <gedmurphy.mailli...@gmail.com
<mailto:gedmurphy.mailli...@gmail.com>> wrote:
You’ve been looking at too many Win10 blue screens
*From:*Ros-dev [mailto:ros-dev-boun...@reactos.org
<mailto:ros-dev-boun...@reactos.org>] *On Behalf Of *Timo Kreuzer
*Sent:* 12 January 2018 20:23
*To:* ros-dev@reactos.org <mailto:ros-dev@reactos.org>
*Subject:* Re: [ros-dev] Making bluescreens more useful
I like it. I recently thought about another possibility to make
the BSOD more useful: A QR code.
A QR code can contain up to almost 3 KB of arbitrary data or 4 KB
text.
Here's a quick example (1425 characters)
Try it out, use your phone and scan it :)
Am 11.01.2018 um 00:48 schrieb Thomas Faber:
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
<https://github.com/ThFabba/reactos/commit/6a9f172b76bd11f763598c16e5d47299eec1971c>
Thoughts?
_______________________________________________
Ros-dev mailing list
Ros-dev@reactos.org <mailto:Ros-dev@reactos.org>
http://www.reactos.org/mailman/listinfo/ros-dev
<http://www.reactos.org/mailman/listinfo/ros-dev>
_______________________________________________
Ros-dev mailing list
Ros-dev@reactos.org <mailto:Ros-dev@reactos.org>
http://www.reactos.org/mailman/listinfo/ros-dev
<http://www.reactos.org/mailman/listinfo/ros-dev>
_______________________________________________
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev
_______________________________________________
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev
_______________________________________________
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev
