Valgrind fails: Possibly corrupted debuginfo file

Hello everyone !

I work on a project in c++, and I use to test it with valgrind to check that I well manipulate the memory. But for a couple of days ago, I can’t run valgrind with some of my own executable files. I mean some of them still work well, but some others, when ran with valgrind, seem to trigger this internal error that I am not sure to understand, neither to know how to fix it:

==18473== Memcheck, a memory error detector
==18473== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
==18473== Using Valgrind-3.19.0 and LibVEX; rerun with -h for copyright info
==18473== Command: ./unit_test.out
### unhandled dwarf2 abbrev form code 0x25
### unhandled dwarf2 abbrev form code 0x25
### unhandled dwarf2 abbrev form code 0x25
### unhandled dwarf2 abbrev form code 0x1b
==18473== Valgrind: debuginfo reader: ensure_valid failed:
==18473== Valgrind:   during call to ML_(img_get)
==18473== Valgrind:   request for range [25217665, +4) exceeds
==18473== Valgrind:   valid image size of 1167576 for image:
==18473== Valgrind:   "/home/jodufour/Documents/42/Cursus/Projects/ft_containers/unit_test.out"
==18473== Valgrind: debuginfo reader: Possibly corrupted debuginfo file.
==18473== Valgrind: I can't recover.  Giving up.  Sorry.

I am using clang 14.0.6 and valgrind 3.19.0

Does anyone could help me please ?

Looking at open bugs yields this report:

Indeed when I looked up about this problem, I found a lot of reports about clang 14 and dwarf5, but I was not sure that was the same problem for me because in my case, it’s about dwarf2.

Ah, missed that.
If no upstream bug report fits your case you might consider opening one.

Okay, got it !

I just looked up to be sure nothing was already opened, and so I opened a new bug report, mentioning this one in the description

because both are quite similar.
Now, all I can do is waiting for my report to be assigned.