Re: NuttX-aware debugging.

Ahhh, so it is your Fedora 36 issue, hahaha Here on Ubuntu "make -C tools -f Makefile.host all" works fine. It created the jlink-nuttx.so file. BR, Alan On 6/22/22, Fotis Panagiotopoulos wrote: > Yes I enabled CONFIG_DEBUG_TCBINFO. > (When disabled, debugging works normally but without being

Re: NuttX-aware debugging.

> 1) Using OpenOCD + GDB: some years ago Mr. Masayuki-san submitted support to OpenOCD get thread awareness; The current support in upstream OpenOCD is outdated. If you want to use OpenOCD maybe you can try building from https://github.com/Ouss4/openocd-esp32/tree/nuttx Although I focused on Xten

Re: NuttX-aware debugging.

Yes I enabled CONFIG_DEBUG_TCBINFO. (When disabled, debugging works normally but without being thread-aware). It seems that it is either a bug in the plugin itself, or something is wrong with my build. If it matters, I am using Fedora 36 with gcc (GCC) 12.1.1 20220507 (Red Hat 12.1.1-1) Maybe so

Re: NuttX-aware debugging.

Did you enable CONFIG_DEBUG_TCBINFO in your defconfig: incubator-nuttx/Kconfig at master · apache/incubator-nuttx (github.com) The plugin needs the g_tcbinfo to know the critical offset of the field in tcb_s structure. On

Re: NuttX-aware debugging.

Hi Fotis, There are two (at least) options to debug NuttX with Thread awareness: 1) Using OpenOCD + GDB: some years ago Mr. Masayuki-san submitted support to OpenOCD get thread awareness; 2) Using Segger JLink + GDB: this is the option you are trying. I think we don't have a documentation to it

NuttX-aware debugging.

Hello, I am in need of debugging NuttX in a thread-aware fashion, as I still hit a dead-lock in networking that I haven't managed to track down yet. I am using a custom target, based on the STM32F427VI and JLink as the debugger. I see that there is a plug-in for JLink GDB that was added in #4810