Debug on the fly of the whole system
This morning, I thought that it would be very cool to be able to debug all the pieces of a system at once: the program being debugged and then the interaction with other software including the OS.
Current debugger allows one program to be debugged. But to debug the various components at once isn't possible today. However, if one was to put all those components into a simulator (like QEMU), then it would be possible to debug them all at once, step by step (depending how accurate the simulator is, you can even get cycle accurate debugging in).
Granted, for most people, such a tool is an overkill. But when your program has interaction problems with the OS and you have access to the source (like Linux), it makes perfect sense to figure where the problem. Or if you are writing a new OS API or functions to help out programs, then you really need such function. Or any embedded systems programming. Or multi-threaded programs across several processors.
Copyright 2007, DannyHSDad, All Rights Reserved.
Current debugger allows one program to be debugged. But to debug the various components at once isn't possible today. However, if one was to put all those components into a simulator (like QEMU), then it would be possible to debug them all at once, step by step (depending how accurate the simulator is, you can even get cycle accurate debugging in).
Granted, for most people, such a tool is an overkill. But when your program has interaction problems with the OS and you have access to the source (like Linux), it makes perfect sense to figure where the problem. Or if you are writing a new OS API or functions to help out programs, then you really need such function. Or any embedded systems programming. Or multi-threaded programs across several processors.
Copyright 2007, DannyHSDad, All Rights Reserved.
posted by DannyHSDad at
7:55 AM
