Re: [Openocd-development] dsp56371 crash

2010-02-14 Thread Mathias K.
Hello, here the patch to fix the crash and create the reg list. Now another Problem with gdb: User : 340 52745 gdb_server.c:106 gdb_last_signal(): undefined debug reason 6 - target needs reset Regards, Mathias Am 14.02.2010 07:33, schrieb David Brownell: On Saturday 13 February 2010,

Re: [Openocd-development] dsp56371 crash

2010-02-14 Thread David Brownell
On Sunday 14 February 2010, Mathias K. wrote: here the patch to fix the crash and create the reg list. Merged, thanks. Now another Problem with gdb: User : 340 52745 gdb_server.c:106 gdb_last_signal(): undefined debug reason 6 - target needs reset I think we've seen that before in other

Re: [Openocd-development] dsp56371 crash

2010-02-13 Thread David Brownell
On Saturday 13 February 2010, Austin, Alex wrote: openocd segfaults upon connecting to it. I've tracked it down to target_get_gdb_reg_list being called when target-type-get_gdb_reg_list is null. Tracing back to where the target-type comes from, it never gets set in dsp563xx.c, so is null. Why

Re: [Openocd-development] dsp56371 crash

2010-02-13 Thread Austin, Alex
To: openocd-development@lists.berlios.de Cc: Austin, Alex Subject: Re: [Openocd-development] dsp56371 crash On Saturday 13 February 2010, Austin, Alex wrote: openocd segfaults upon connecting to it. I've tracked it down to target_get_gdb_reg_list being called when target-type-get_gdb_reg_list is null

Re: [Openocd-development] dsp56371 crash

2010-02-13 Thread David Brownell
On Saturday 13 February 2010, Austin, Alex wrote: The GDB in question is the gdb56300.exe provided by freescale, running under WINE. I had the source for it at one time, but I've somehow managed to misplace it. Yeah, that's what you'd want to have OpenOCD work with. If it's not