Memory Inspector does not resolve variable addresses

[NSAUG.1]

Hello,

In a paused debugging session, in the Run and Debug > Variables > Local list, if I right-click the varaible, the context menu has an item "Show in Memory Inspector".

Clicking it opens the Memory Inspector, but with the name of the variable as the adress ( &(pRxData) for example), which the memory viewer cannot resolve into the actual address (0x20003DC0 for example).

For this functionality to be most useful, I would expect either the Memory Inspector to be able to resolve the variable, or the command to open the Memory Inspector with the already-resolved address.

Best regards,

Nicolas

[Mikk Leini]

I see the issue also, but only with some local stack based variables. Global and static variables work fine.

Using vscode with STM32Cube extensions v3.7.0, STLINK-V3MINIE and STM32N65x0 MCU. GCC compiler and -O2 optimization.

[Nawres GHARBI]

@NSAUG.1  thanks for reporting this issue ticket #3953  logged for fix