python3 debugging symbols CRC error in kirkstone

I'm trying to debug a memory leak in a python application of ours that uses a c module, however what seems to be the tool for the job these days (memray)  is categorising the bulk of allocations into an <unknown> field.

After a bit of digging it turns out this seems to be relating to some problem with how the python packages are being produced.

readelf -S /usr/bin/python3.10 | grep debug
[26] .gnu_debuglink    PROGBITS         0000000000000000  00003010
readelf: Warning: Separate debug info file /usr/bin/python3.10 found, but CRC does not match - ignoring

I have tried bitbake -c clean python3, rebuilding with --runall=build and reinstalling packages on the target but the issue persists.
Strangely the file it reports as a separate debug info file is actually the same file as the binary not the debug info file which is installed as /usr/bin/.debug/python3.10

How do I resolve this?

I tried to isolate and reproduce the leak in a standalone application to debug on another platform but unfortunately the leak is not happening here.