Earlier quoted context omitted.
It’s a terrible shame Linux is still a 1970s program. Plan 9’s debugger Acid can attach to a running kernel on a remote machine and debug it.
> It’s a terrible shame Linux is still a 1970s program. This is a needlessly snide and inaccurate characterization. > Plan 9’s debugger Acid can attach to a running kernel on a remote machine and debug it. KGDB over Ethernet does the same on Linux.
ELF Crimes: Program Interpreter Fun
11–15 of 15 posts
Re: ELF Crimes: Program Interpreter Fun
#12Earlier quoted context omitted.
> It’s a terrible shame Linux is still a 1970s program. This is a needlessly snide and inaccurate characterization. > Plan 9’s debugger Acid can attach to a running kernel on a remote machine and debug it. KGDB over Ethernet does the same on Linux.
Emulating a serial terminal emulating a teletypewriter emulating a punch card system.
Re: ELF Crimes: Program Interpreter Fun
#13Earlier quoted context omitted.
Emulating a serial terminal emulating a teletypewriter emulating a punch card system.
If it works what do I care?
I'm guessing you've never tried to write a terminal rendering program.
The hoops you hav to jump through to get vi to switch into a blank screen and then drop back and re-render your previous terminal.
Behaviour differences on some terminals when you run man and the previous output is simply cleared or the man page is printed and scrolled.
There are piles of hacks.
Re: ELF Crimes: Program Interpreter Fun
#14Earlier quoted context omitted.
If it works what do I care?
Because making it work is burdensome and writing programs that interact with it even more so. I'm guessing you've never tried to write a terminal rendering program. The hoops you hav to jump through to get vi to switch into a blank screen and then drop back and re-render your previous terminal. Behaviour differences on some terminals when you run man and the previous output is simply cleared or the man page is printe…
Re: ELF Crimes: Program Interpreter Fun
#15Earlier quoted context omitted.
Because making it work is burdensome and writing programs that interact with it even more so. I'm guessing you've never tried to write a terminal rendering program. The hoops you hav to jump through to get vi to switch into a blank screen and then drop back and re-render your previous terminal. Behaviour differences on some terminals when you run man and the previous output is simply cleared or the man page is printe…
Ok, but what does this have to do with kernel debugging?