GDB commands supported?

[Andrea Aizza]

Hi, 

when debugging nRF52 chips, currently using nRF52840-DK with arm-none-eabi-gdb (version 8.2.50.20181213-git), is the use of 'commands' supported? 

Trying to see some content of ble_evt_handler but fails with SIGTRAP:

(gdb) i b
Num     Type           Disp Enb Address    What
8       breakpoint     keep y   0x0002c2a0 in ble_evt_handler at ../../../main.c:388
        p p_ble_evt->header.evt_id
        c
(gdb) mon reset 1
Resets the core only, not peripherals.
(gdb) c
Continuing.

Breakpoint 8, ble_evt_handler (p_ble_evt=0x2000fc84, p_context=0x0) at ../../../main.c:392
392         ble_gap_evt_t const * p_gap_evt = &p_ble_evt->evt.gap_evt;
$1 = 29

Program received signal SIGTRAP, Trace/breakpoint trap.
0x000279e8 in app_error_fault_handler (id=<optimized out>, pc=<optimized out>,
    info=<optimized out>) at ../../../../../../components/libraries/util/app_error_weak.c:100
100         NRF_BREAKPOINT_COND;
(gdb) bt
#0  0x000279e8 in app_error_fault_handler (id=<optimized out>, pc=<optimized out>,
    info=<optimized out>) at ../../../../../../components/libraries/util/app_error_weak.c:100
#1  0x00024008 in ?? ()

Any hint or thing I am doing wrong?

[Håkon Alseth]

Hi,

 

"bt full" should give you the full call stack, but if your optimization level is high, chances are it's not going to give you much.

I would recommend that you add CFLAGS += -DDEBUG to enable blocking assertions, and reduce the optimization to "-O0 -ggdb".

 

Kind regards,

Håkon