Re: NuttX-aware debugging.

> Could you try this patch? I just tried it, and it works correctly. Thank you! Also, can you please check whether you can build the plug-in with -fPIC? If it is needed for some distros, and it is not harmful for the rest, we may add it permanently. On Sat, Jun 25, 2022 at 3:34 PM Xiang Xiao

Re: NuttX-aware debugging.

On Fri, Jun 24, 2022 at 5:42 PM Fotis Panagiotopoulos wrote: > Hello everyone! > > I got it working. > > Good luck. > The issue is in RTOS_SetThreadReg(). > For some reason g_plugin_priv.tcbinfo is NULL. > > I added a simple check: > > if (g_plugin_priv.tcbinfo == 0) > { > return

Re: NuttX-aware debugging.

Hello everyone! I got it working. The issue is in RTOS_SetThreadReg(). For some reason g_plugin_priv.tcbinfo is NULL. I added a simple check: if (g_plugin_priv.tcbinfo == 0) { return -EINVAL; } And now it works correctly. I can submit a PR, however I have no idea how this

Re: NuttX-aware debugging.

We document the JLinker plugin usage, but it's the Chinese version only. Pengxiang, please prepare a document. In the meantime, Fotis, could you attach gdb to JLinkGDBServer and print the backtrace when it crashes, so we can identify the reason quickly. On Thu, Jun 23, 2022 at 10:36 PM Alan

Re: NuttX-aware debugging.

Please describe all the steps you are doing and such way everybody can reproduce yet (same way I did in previous email). I don't think a library compile to Ubuntu will work on Fedora. Xiang, do you have a documentation about the JLink integration? BTW, any news about the guy/gal Xiaomi was

Re: NuttX-aware debugging.

I tried your instructions. The build fails on a clean repository too. I then tried a newer version of Ubuntu (as a Docker container, I do not have access to any other Ubuntu machines). This time the build succeeded. However I haven't managed to debug the application from within this Docker

Re: NuttX-aware debugging.

Hi Fotis, I'm using Ubuntu 20.04 and I can confirm it is working fine, I don't need to add -fPIC. Please try a clear repository, I will do it here step-by-step on /tmp to removed after next reboot: $ cd /tmp/ $ git clone https://github.com/apache/incubator-nuttx nuttx $ git clone

Re: NuttX-aware debugging.

> Ahhh, so it is your Fedora 36 issue, hahaha No, it is not. I just tried on Ubuntu 18, and I got the exact same result. Build fails with the same error. I added the -fPIC flag, and the build succeeded. Then I tried to debug the firmware with JLink and GDB crashes during init with a SEGFAULT.

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

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

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