[ros-kernel] BSOD really intentional?
tamlin at algonet.se
Thu Jan 8 22:38:11 CET 2004
Due to recent changes in the registry code in the kernel, it kept crashing
without telling me anything but CONFIG_INITIALIZATION_FAILED.
The reason for the crash was an incompatibility between me not having
updated the registry, and current ROS changes starting to require the key
"Registry\Machine\SYSTEM\Select" and all four values it was looking for.
While I probably have to accept that change, I'm not too happy about it
forcing me running around in the kernel adding "printf-debugging" to see
what really failed. CONFIG_INITIALIZATION_FAILED is itself vague enough to
mean just about anything.
So, my question(s): Is it the intention that ROS shall crash on startup if
this key, or any of the values it's looking for, is not found?
If yes, could it perhaps be considered, as a curtesy to the user of the
system, to actually tell the user in more precise words what went wrong? I
do mean with the precision that if the value "Failed" is missing, the code
would tell me
"I could not find the registry value Machine\SYSTEM\Select\Failed. This is a
terminal error. Thank you for your understanding, and have a nice day."
before, for all intents and purposes, going tits up and crashing on me.
Wouldn't that make more sense than just saying:
More information about the Ros-kernel