Symbol not included in compiled hex file

[daubsi]

I am debugging an application on a nRF5340 DK using nRF Connect SDK from VS Code. (Toolchain/nRF Connect SDK v2.9.0), everything up-to-date.

The build is "optimized for debugging".

When I set a bp in an interesting function I want to see the actual contents of an array which is manipulated.

From the context menu I select: "Reveal symbol in memory explorer" but get the error "The symbol XYZ is not included in the compiled hex file".

Actually I don't see any of my user-defined variables in the selection box. 

What do I need to do to properly see the memory area and contents of a variable I want to inspect?

[Hung Bui]

Hi Markus, 
Do you have a minimum sample that demonstrate the issue so we can test here ? 
When you debug,  do you see the value of for example tx_buffer[] array ? 
Can  you step in the code normally ? 
Could you try adding CONFIG_DEBUG_OPTIMIZATIONS=y  to prj.conf? 

[daubsi]

Hi Hung Bui,

you can actually have a look a the actual code I am working on right now as an example:

https://github.com/OevreFlataeker/nrf5340_ak_fx/commit/b4e0165ffd8b9702624681fbc0f53c01492cb87d

My assumption is that I can "lookup" all the variables, structs, etc. in the Memory explorer just like when I do a "Add to watch" in order to keep them in scope, correct?

[Hung Bui]

Hi Markus, 
I found that I can lookup for the global or static variable but not the dynamic allocated variable. If you click on the plus sign and select ELF symbol you can find the static variable. 

My understanding is that Memory Explorer doesn't follow dynamic variable. I will check internally to get this confirmed. 

[daubsi]

Thank you Hung Bui. But why do I even need to use that special option of looking up an ELF symbol? What's different to the symbols I CAN find with the other options?