AnsweredAssumed Answered

Program received signal SIGINT, Interrupt. when not sent. Why?

Question asked by Bob Paddock on Jan 21, 2016


I'm trying to debug somecode with USBDM 4.12 70 and GDB on Windows 7x64.
Part is KL27Z256M4 Chip ID 23161D85.

 


Alas then I try to run the code via GDB I keep getting:

 

"Program received signal SIGINT, Interrupt."

 

I am NOT pressing Control-C to stop the program.

 

GDB is just stuck on this first line line of the program,
next, step and continue are all stuck here.

 

What is going on?

 


GNU gdb (GNU Tools for ARM Embedded Processors) 7.8.0.20150604-cvs
This GDB was configured as "--host=i686-w64-mingw32 --target=arm-none-eabi".

 

(gdb) target remote :1234
Remote debugging using :1234
_reset_init () at HRD_MKL27Z4_TP5/vectors.c:323
323      irq_disable(); /* Did bootloader leave IRQs on perhaps? */

 

(gdb) list
318      */
319    extern size_t  __data_load_size__;
320    extern uint32_t __ram_start, __data_load_start__, __data_start__;
321    void _reset_init(void)
322    {
323      irq_disable(); /* Did bootloader leave IRQs on perhaps? */
324
325      SCB_VTOR = (uint32_t) interrupt_vector_table;
326      sync_barrier_data();
327
(gdb) c
Continuing.

 

Program received signal SIGINT, Interrupt.
_reset_init () at HRD_MKL27Z4_TP5/vectors.c:323
323      irq_disable(); /* Did bootloader leave IRQs on perhaps? [This is the first executable line of vectors.c] */
(gdb)

Outcomes