> > gdbstubs is also not terribly SMP aware and for low level work its > > sometimes easier to have on gdb per processor if you can get your brain > > around it. > > That's a trick I don't know. What do you do, fire up the target > process, put the whole thing to sleep with a SIGSTOP, and then attach > a separate gdb to each thread after they've been migrated and locked > down to the destination CPU?
gdbstubs/kgdbstubs is kernel side so you boot the two cores and each core halts in the debugger on a breakpoint trap. One debug stub uses one serial port (or one UDP port), the other uses a different one. Two gdbs and you can stop/play with each processor independently. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
