On 2014-05-30 15:03, Peter Dufault wrote:
On the Phytec MPC5554 with the current head as of yesterday I'm having funny problems with GDB and the McGraigor wiggler. I don't need to use this setup that often so everything has changed since I last used it: GCC, GDB, RTEMS, the version of Linux, the McGraigor driver... So I'm at basic principles.If I just start the program, interrupt with ^C, and continue it exits. I start, hit ^C, and enter GDB. I'm in the idle thread, as you would expect. I have a hardware breakpoint set in bsp_reset(), which is the fatal handler. This "c" below is the initial setup and will start the program. Then I type the ^C: ==== (gdb) c Continuing. ^C Program received signal SIGTRAP, Trace/breakpoint trap. bsp_idle_thread (arg=0x0) at ../../../../../../../../rtems/c/src/lib/libbsp/powerpc/mpc55xxevb/startup/idle-thread.c:30 30 mpc55xx_wait_for_interrupt(); (gdb) ==== Now when I continue I will hit the breakpoint in bsp_reset:
Maybe the debugger has a problem with the wait instruction? -- Sebastian Huber, embedded brains GmbH Address : Dornierstr. 4, D-82178 Puchheim, Germany Phone : +49 89 189 47 41-16 Fax : +49 89 189 47 41-09 E-Mail : sebastian.hu...@embedded-brains.de PGP : Public key available on request. Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG. _______________________________________________ rtems-devel mailing list rtems-devel@rtems.org http://www.rtems.org/mailman/listinfo/rtems-devel
