• State Not Answered
  • Replies 5 replies
  • Subscribers 87 subscribers
  • Views 371 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 350473
Options

VScode in nRFConnect removes -DCONFIG_DEBUG_THREAD_INFO=y since end of August 2025

cellular_iot

Hi all,

Full debug builds (-Og) of lwm2m_client simply don’t fit into the nRF91xx targets (nRF9151 DK, Thingy91, Thingy91x).
As a workaround I found that building with size optimization (-Os) and explicitly enabling essential debug symbols via:

-DCONFIG_DEBUG_THREAD_INFO=y

…actually works. With that, I can build and debug inside VSCode without problems.

But: since I had to reinstall VSCode and nRF Connect last Friday, I now need to manually add -DCONFIG_DEBUG_THREAD_INFO=y before each build. nRF Connect just keeps removing it from the build config. That means before every build I have to check if it’s still there – otherwise the image can’t be debugged, and I end up re-creating the config and doing a full rebuild… only to repeat the same next time.

Is there really no persistent way to keep such options?

I wonder sometimes if anybody at Nordic is actually using the “preferred setup” (VSCode + nRF Connect on Windows 11) day to day. For me, even very basic things keep breaking on almost a daily basis…









Parents
  • 0

    I had to deinstall, reinstall, "install specific version" of all 4 Nordic extensions to find an older combo which 1) works together 2) doesnt randomly delete my config settings 3) doesnt consume endless CPU power: "nrf Connect 2025.5.152" is the current way to go.

  • 0 in reply to cellular_iot

    Hello, 

    Thank you for the report. I have forwarded the report internally. The responsible team may want some more information to diagnose the issue if they are not able to reproduce it. Could your share the support information ( ) for both releases: 2025.5.152 and 2025.8.654? 

    Is there really no persistent way to keep such options?

    A way which does not rely on extra CMake arguments is to create a Kconfig fragment with  CONFIG_DEBUG_THREAD_INFO=y and add it to the Extra Kconfig fragments field. 

    Best regards,

    Maria

Reply
  • 0 in reply to cellular_iot

    Hello, 

    Thank you for the report. I have forwarded the report internally. The responsible team may want some more information to diagnose the issue if they are not able to reproduce it. Could your share the support information ( ) for both releases: 2025.5.152 and 2025.8.654? 

    Is there really no persistent way to keep such options?

    A way which does not rely on extra CMake arguments is to create a Kconfig fragment with  CONFIG_DEBUG_THREAD_INFO=y and add it to the Extra Kconfig fragments field. 

    Best regards,

    Maria

Children
Related
Terms of service