Hi im having a problem debugging and was wondering if anyone else had similar problems, jtag device seems to get stuck on a particular line, i have also encountered errors such as stack corrupted etc. was wondering if there is a web page that explains these common errors and why they happen etc below is gdb output of my problem, I was debugging tinyos 2.x thanks Cormac
Connection opened by host 127.0.0.1, port 53129. 0x00000000 in __vectors () (gdb) break main Breakpoint 1 at 0xe4: file /opt/tinyos-2.x/tos/system/RealMainP.nc, line 62. (gdb) c Continuing. Breakpoint 1, main () at /opt/tinyos-2.x/tos/system/RealMainP.nc:62 62 call Scheduler.init(); (gdb) list 57 tasks. Initialize all of the very hardware specific stuff, such 58 as CPU settings, counters, etc. After the hardware is ready, 59 initialize the requisite software components and start 60 execution.*/ 61 62 call Scheduler.init(); 63 64 /* Initialize the platform. Then spin on the Scheduler, passing 65 * FALSE so it will not put the system to sleep if there are no 66 * more tasks; if no tasks remain, continue on to software (gdb) 67 * initialization */ 68 call PlatformInit.init(); 69 while (call Scheduler.runNextTask()); 70 71 /* Initialize software components.Then spin on the Scheduler, 72 * passing FALSE so it will not put the system to sleep if there 73 * are no more tasks; if no tasks remain, the system has booted 74 * successfully.*/ 75 call SoftwareInit.init(); 76 while (call Scheduler.runNextTask()); (gdb) n Breakpoint 1, main () at /opt/tinyos-2.x/tos/system/RealMainP.nc:62 62 call Scheduler.init(); (gdb) n Breakpoint 1, main () at /opt/tinyos-2.x/tos/system/RealMainP.nc:62 62 call Scheduler.init(); (gdb) n Breakpoint 1, main () at /opt/tinyos-2.x/tos/system/RealMainP.nc:62 62 call Scheduler.init(); (gdb) _______________________________________________ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
