The program I was going to use to debug the hardware uses the exact same mechanism that’s broken and needs debugging. Royal suckage.
October 27, 2003
4 Comments »
RSS feed for comments on this post. TrackBack URI
The program I was going to use to debug the hardware uses the exact same mechanism that’s broken and needs debugging. Royal suckage.
RSS feed for comments on this post. TrackBack URI
Don’t you use the fabulous…
…kernel debugging library? IIRC it’s called printk…
Comment by Anonymous — October 27, 2003 @ 3:58 AM |
Re: Don’t you use the fabulous…
printk is good for telling me what the kernel thinks it’s sending to the hardware. It’s useless for telling me what the hardware is actually seeing …
Comment by mulix — October 27, 2003 @ 6:32 AM |
Re: Don’t you use the fabulous…
How can a debugging facility do that? (probe the hardware to get what its seeing.
Comment by Anonymous — October 27, 2003 @ 8:30 AM
Re: Don’t you use the fabulous…
In this case, the hardware is a disk controller that knows how to dump its memory and the debugging facility knows how to retreive it. Unfortunately, retrieving the dump uses the exact mechanism we’re trying to debug.
Comment by mulix — October 27, 2003 @ 1:03 PM