On Mon, Jun 18, 2012 at 04:57:26PM -0500, jim norris wrote: > Frank, > > FYI, gdb does not know about multicore / processor platforms. > > Jim
Hi Jim, Ok. Do you think the stepping problems I've discovered is due to that limitation? I'm doing the following when debugging: 1) Start openocd 2) Telnet to openocd and halt both cpus. It seems that I need to halt at least one of the cores in order to be able to establish contact from gdb (ie. tar rem :3333 don't work if I don't..). Is this normal? 3) Start gdb (currently use the newest arm linaro version). 4) Halt both cpus (again) and check via "mon targets" 5) c/continue and observe that U-Boot is alive 6) Resume from gdb via Ctrl-C works, but I noticed now that I also get a STICKY error when doing so. However, the resume operation works.. so it seems that the transition from "halted" to "running" is correlated to the problem with stepping. 7) If I now run "targets" from the telnet session, I only see one of the cores running. This is as intended, since I assume that most operation are applied to the current selected target. Since only one of the cores are "selected" and running during the debugging session, I assume that the single core limitation in gdb wouldn't be a problem. Are my assumptions correct? Best regards, Frank ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
