http://scholar.harvard.edu/files/mickens/files/thenightwatch.pdf

"When you debug a distributed system or an OS kernel, you do it Texas-style. You gather some mean, stoic people, people who have seen things die, and you get some primitive tools, like a compass and a rucksack and a stick that’s pointed on one end, and you walk into the wilderness and you look for trouble, possibly while using chewing tobacco. "

@Mr_Capehill

I do not think many will get this, but I do, working on Catweasel MK4 driver for AmigaOS4.0, for every time you make change the device, crashes, it can be unloaded, the system frizzes, for every time you need to power down system completely with the Power button. Because CTRL+AMIGA+AMIGA is not working, system froze and you can retrieve the debug log, a real pain. Sometimes Memory protection, work some time it does not, sometime device corrupt itself. I do not know about walking dead or not, but its real torture.

I guess some have less problems with torture then others. I guess that’s way most of the drivers are made by the same people, or maybe they are more careful to not shoot them self in the foot, I don't know.

Last edited by NutsAboutAmiga on 04-Jul-2017 at 06:58 PM.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@NutsAboutAmiga

Quote:

for every time you make change the device, crashes, it can be unloaded, the system frizzes, for every time you need to power down system completely with the Power button

That pretty much summarizes my short foray into Linux kernel hacking. Userspace is serene by comparison.

_________________
"Unix is supposed to fix that." -- Jay Miner

@bison

Debugging a UBoot app can be hard. I've done it. So it loads up and then instantly crashes. You see a brief moment on screen where there was a crash log. But you can get it with a debug cable. You look at the output. It makes so sense. UBoot didn't even have the courtesy to look up any of those symbols you compiled in. You're on your own. Offsets are as good as offsets into OS4 kernel space with no clue or table to look up. So it's down to the old and obtuse method of plugging in printf() calls. Recompile. Copy to boot medium unless your setup allows to copy direct to a file. Writing a boot CDRW every time is not efficient. Check new version to see what it gets up to and if you found it yet. As the old saying goes. Now it's rinse and repeat.

Last edited by Hypex on 05-Jul-2017 at 03:05 AM.