When ddb works, it is a useful tool for debugging system problems.
However my experiences (and those of others, it seems) suggest that
it isn't quite 100% reliable.

Sure it is easy enough to work around this but just not compiling
it in, but then when you do want it, it's not there.  Or if you
put it in, it is possible for accidents to interfere with operation.

Letting my thoughts crystalise...

There are two things I want from ddb:
- it to be available whenever I want it and
- to not interfere with anything unless it is enabled

At present, we can make it available, all the time but we can't
disable it.  Why is this a problem?  Because having it enabled
appears to expose the system to hanging if it is in a bad way
and ddb is involved - hangs that aren't otherwise likely.

Admitedly this almost guarantees that when I want it, it'll be
disabled (to attempt to ctrl-alt-esc) but that's something I am
prepared to live with.


This is driven mostly by there being two desires for the system to
operate - one when I'm around and one when I'm not - and it shouldn't
take a reboot to go from one to the other.  When I'm around, I want
ddb enabled, when I'm not, I don't.  The "don't" includes not wanting
any risk of ctrl-alt-esc being somehow activated.

Comments ?