To view parent comment, click here.
To read all comments associated with this story, please click here.
One of the possible causes of the kernel panic is not being able to access said device, so where do you suggest to write the log?
But let's say you actually dump the file. What if the system doesn't boot anymore? Do your move the partition / drive to a different Haiku machine?
Do you realize this is an, WIP OS with no stable release right?
Edited 2012-07-03 00:14 UTC
Writing data to a storage device requires a lot of hardware control to *still* work. What happened when the boot device is an USB one and the panic is due to USB bus controler or its driver code? How do you write anything to a data storage device in such case?
Same goes for ATA bus, which is not *that* trivial to access.
Meanwhile, displaying data is simple: just write bytes at a well-known address within framebuffer addresses range. Simple and highly reliable.
What was not simple and reliable was copying the data displayed that way.
Edited 2012-07-03 09:35 UTC




Member since:
2010-01-11
I LOL'd. ^_^
It's just an extra feature to aid in the process of reporting bugs when the kernel crashes. The old method of taking a screenshot using a camera still works fine.
As for me, I don't have a smart phone