PIO debugger not showing variables in variables window

I (somehow) managed to get PIO debugging to work on a simple program, I can set breakpoints, step etc, and even hover over a variable to see its current value - but - I can’t find a way to have the debugger populate the variables window (and show the values). I do get an error during PIO initialising remote target (part of debug console output showing error)

========================= [SUCCESS] Took 5.58 seconds =========================
Reading symbols from c:\Users\SteveV\Documents\PlatformIO\Projects\Next1.pio\build\nanoatmega328new\firmware.elf…
done.
PlatformIO Unified Debugger → Redirecting...
PlatformIO: debug_tool = avr-stub
PlatformIO: Initializing remote target…
__udivmodsi4 () at …/…/…/…/gcc/libgcc/config/avr/lib1funcs.S:1648
1648 …/…/…/…/gcc/libgcc/config/avr/lib1funcs.S: No such file or directory.
PlatformIO: Initialization completed
PlatformIO: Resume the execution to debug_init_break = tbreak main
PlatformIO: More configuration options → Redirecting...

Is the missing file the reason why the variables are not shown?
If yes, where should it be and how should it be included??

Also, I get an ‘task error’ as follows:

Error: The PlatformIO task detection didn’t contribute a task for the following configuration:
{
“type”: “PlatformIO”,
“task”: “Build (nanoatmega328)”,
“problemMatcher”: [
“$platformio”
],
“group”: “build”,
“label”: “PlatformIO: Build (nanoatmega328)”
}
The task will be ignored.
Error: The PlatformIO task detection didn’t contribute a task for the following configuration:
{
“type”: “PlatformIO”,
“task”: “Build (nanoatmega328)”,
“problemMatcher”: [
“$platformio”
],
“group”: “build”,
“label”: “PlatformIO: Build (nanoatmega328)”
}
The task will be ignored.

Is this a problem? how do I fix or make it go away?
I Hope you can assist (an extremely inexperienced person with the modern tools - I last did embedded programming a little over 30 years ago!!)
Cheers

You may be hitting https://github.com/platformio/platformio-vscode-ide/issues/2334, which is unique to AVR + avr-debug (and not other platforms), use right-click + Add variable to watch as a workaround.