On 2/11/2011 11:45 PM, Andrew Dennison wrote: > Normally you would maintain a debug context for each process, and swap > the debug context as part of the task switch - the OS needs to > cooperate in this exercise. I've done this for some simple debug > support using the hardware debug support in our target processor: I'll > setup a gdb stub one day.
What I'm not sure about is how to get gdb to take advantage of that, especially e.g. via the QEMU debug stub. On the other hand, I can easily see how to create a couple of debug operations to allow one thread to get/set another's registers, and to single-step a thread; given this it should be straightforward to add a thread to a process which implements the gdb remote protocol. > I haven't played with qemu debug - I've only used qemu for some basic > sanity checking that I haven't broken the architectures I don't have > hardware for. It's more useful if you're working with the PC platform. All the devices are supported out of the box, plus there's no such thing as a JTAG port on a PC :-) -- ..................................................................... Peter Desnoyers [email protected] Northeastern Computer & Information Science ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Prex-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/prex-devel
