Besides, when you're rooted it's game over anyway.
We'd see this problem a lot with calling conventions (C-style vs Pascal-style vs pretty much any weird thing you found a reason to do) if our gdb-based debuggers tried harder to figure out what was going on. Luckily, they rarely really bother and are wrong constant anyway about things like optimization -- they're built to do fairly little and live in constant confusion, so we don't get that problem.
And for the record, I like gdb and company. But every so often I get a wet dream about being able to have a debugger that could show me useful representations of objects and what they do. Things are better in Ruby-land, but still not actually, like, good.
They had a radical open system, and defended it (yes, it was early in the life of the ARPAnet/Internet) with great backups and social pressure.
The LispMs were not much different.
EDIT: Except for the whole-machine-IDE thing, obviously. Although if you wanted to hand-hack assembler, you could, as far as I remember.
You programmed in the absolute using the alt-numpad method to input arbitrary bytes, at least to bootstrap yourself.