Here is a Kernel ASLR implementation for NetBSD-amd64. [...]
Contrary to what has been said in previous discussions, KASLR does
not alter debugability in any way: the symbols are still mapped in
memory as they are right now, and ddb resolves them as usual.
I disagree that that's enough to "not alter debugability in any way".
It makes common debugging tasks work, perhaps, but I have occasionally
run into cases where all I have is a pc value (even less often, but
it's still happened, a data address) and have had nothing but /netbsd's
symbol table to help me make sense of it.