Hello Jon, Tuesday, July 28, 2009, 10:28:37 PM, you wrote:
JB> I'm porting OpenOCD to a new processor architecture and I've noticed that JB> there doesn't appear to be any support for the X and F GDB Stop Reply JB> Packets JB> (http://sourceware.org/gdb/current/onlinedocs/gdb_34.html#SEC724), JB> which are used to indicate that a process has exited (X) or to perform JB> system calls on the host (F). You're looking at this from the wrong side. The GDB "server" in OpenOCD is what is called "stub" in the documentation. It does not need to support F or X; those need to be implemented on the host side _if_ the stub is going to send them. And I don't see a situation when OpenOCD would send those. (Well, I guess it could send X if it loses connection with the target...) JB> Also, there doesn't currently appear to be any support for signals other JB> than SIGINT & SIGTRAP. I think it would be useful if other common signals JB> such as SIGBUS, SIGILL and SIGSEGV could also be passed on, when applicable. Those are all user-mode signals. Since OpenOCD works on the lowest level (JTAG), it doesn't know about processes. It can only report events from hardware (such as breakpoints). I guess one _could_ install a custom prefetch abort handler and convert it to a SIGBUS... but it's much more likely that OpenOCD user is debugging a kernel or an RTOS which has its own handler. JB> Looking at server/gdb_server.c, it should be fairly straight forward to do JB> by adding a few additional DBG_REASON_s. There shouldn't be any issues for JB> targets that don't support them - as the code will not be executed. JB> If I create a patch to add support for this, is it likely to be accepted, or JB> is there a reason there is no support for this? -- WBR, Igor mailto:skochin...@mail.ru _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
