I was eyeballing the field for a while, but every time I am almost ready to dive in, something at work pops up and I spend weeks debugging crashes in 3d party code. Let me tell you, you work w/ WinDBG w/o source or symbol files for some time, and everything w/ hexadecimal in it starts getting on your nerves
And that's when you can step over the instructions. Here you just have to stare at it...
I understand that aftermarket deals mostly w/ the data sections, but I wonder how they debug the actual code at Ford. In Windows kernel for example one can connect through serial port and debug from a remote machine, so your debugee machine sits and does literally nothing untill you press F10. But that's not possible w/ the engine running, so they must have an emulator of some kind... Last time I thought about it, this seemed to be the most interesting field because once you've got an emulator you can actually run the code in the debugger and see exactly what it's doing and when. But even this is not easy to approach, because from what I know Ford code is no longer 8086 assembly...
)
