Linked by Thom Holwerda on Mon 2nd Jul 2012 18:19 UTC, submitted by anonymous
BeOS & Derivatives Michael Lotz added code to generate QR-code for the KDL (Kernel Debug Land) ouput (which pops up when the kernel crashes). No more blurry photos with debug output, but a QR code which decodes to the clear-text KDL debug output. Here's one of the relevant commits, an example showing a QR code, and text from decoded sample QR code.
Thread beginning with comment 524863
To view parent comment, click here.
To read all comments associated with this story, please click here.
by galvanash on Mon 2nd Jul 2012 23:49 UTC in reply to "WTF IS THIS SHIT"
Member since:

Who thought this was a good idea?

Lets use a smart phone to decode the error message ... Why not I dunno write some data to disk? Surely that would have been simpler.

You are completely missing the point. The information being displayed is of no use at all to an end user. On Windows you get stop codes - are you saying a stop code conveys useful information to the user? It is a completely meaningless number...

Haiku is not Windows or Linux. The userbase is very small and is under rapid development. Googling stop codes or other such nonsense to try and figure out why something is going wrong (as an end user) is likely to be very hit or miss, mostly miss. The real purpose of the information is to allow a kernel developer to determine what went wrong. That is, btw, the real purpose of the information for Windows too - the fact they you can often look up stop codes on the web and gleam out what is going on from them is due to its popularity - nothing more.

More importantly though, for it to be of any use to anyone it has to be communicated to the developer... How exactly do you get the debug log off the hard-drive of the machine that doesn't work reliably???

The whole point is to make it simple to communicate the information to a developer. It is much cleaner to get an easy to decipher QRCode than it is to try and squint it out of a bad photo of a monitor.

Sure, the stop code approach (which serves roughly the same purpose) works too, but stop codes are just keys to a lookup - the stop code itself means nothing unless you already know where in the code they get hit. Using QR codes you can actually put a fair amount of meaningful information INTO the "stop code".

I suspect Haiku is not far enough along yet to get religious about how they handle kernel panics internally, different subsystems likely dump/panic in different ways (with differing levels of detail). This is a catchall mechanism to deal with the issue of inconsistent error handling.

I would like to see something as consistent as stop codes used for Haiku as well one day, but I think this QR code thing is a lovely idea for the time being. And it will remain useful even if they get to that point (as a way to convey additional information).

Reply Parent Score: 3