Re: does Valgrind-3.19.0.GIT support Clang14 dwarf 5?
"ISHIKAWA,chiaki" <[email protected]>
| Newsgroups | gmane.comp.debugging.valgrind |
|---|---|
| Message-ID | <[email protected]> |
This is tangent to the original question, but this part: > with split-dwarf (which rnglistx and strx form codes doesn't support yet) valgrind does support bulk of data generated by --split-dwarf (gcc), doesn't it? The above refers to "doesn't support" rnglistx and strx form codes? I am asking this because I have checked mozilla thunderbird code which is compiled using --split-dwarf of GCC and valgrind reports reasonably sane diagnosis so far. Well, that is what I thought. Maybe I was mistaken. Will you kindly clarify the above? TIA Chiaki Ishikawa On 2022/02/14 17:02, Mark Wielaard wrote: > Hi Thomas, > > On Sun, Feb 13, 2022 at 08:18:48PM +0000, Thomas Wollenzin wrote: >> This is a just a quick question. As I haven't found a sufficient answer in the archives. >> Does Valgrind-3.19.0.GIT support Clang14's dwarf5 yet? >> >> Compiling my application with '-gfull -gdwarf-4 -gdwarf64' allows valgrind to function as expected. >> When using `-gfull -gdwarf-5 -gdwarf64` I get this failure report. >> >> ==139537== Memcheck, a memory error detector >> ==139537== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. >> ==139537== Using Valgrind-3.19.0.GIT and LibVEX; rerun with -h for copyright info >> ==139537== Command: ./TheAppName >> ==139537== Parent PID: 139504 >> ==139537== >> ### unhandled dwarf2 abbrev form code 0x25 >> ### unhandled dwarf2 abbrev form code 0x25 >> ### unhandled dwarf2 abbrev form code 0x25 >> ### unhandled dwarf2 abbrev form code 0x23 >> ==139537== Valgrind: debuginfo reader: ensure_valid failed: >> ==139537== Valgrind: during call to ML_(img_get) >> ==139537== Valgrind: request for range [11350107, +4) exceeds >> ==139537== Valgrind: valid image size of 1584416 for image: >> ==139537== Valgrind: "/path/to/TheAppName" >> ==139537== >> ==139537== Valgrind: debuginfo reader: Possibly corrupted debuginfo file. >> ==139537== Valgrind: I can't recover. Giving up. Sorry. >> ==139537== > As you can see above, valgrind doesn't. clang uses rnglistx and strx > form codes, which are normally (by gcc) only used with split-dwarf > (which valgrind doesn't support yet). Best is to simply use -gdwarf-4 > with clang. > > Cheers, > > Mark > > > > _______________________________________________ > Valgrind-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/valgrind-users > _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users