[PATCH] tests: fix for toolchains producing compressed debug sections

Mark Wielaard mark@klomp.org
Tue Mar 23 14:20:12 GMT 2021


Hi Dmitry,

On Mon, 2021-03-22 at 20:00 +0000, Dmitry V. Levin wrote:
> When toolchain produces compressed debug sections by default,
> quite a few debugedit tests fail because of unexpected
> "debugedit: ./foo.o: DWARF version 0 unhandled" error diagnostic messages:
>   3: debugedit .debug_str objects DWARF4             FAILED (debugedit.at:97)
>   4: debugedit .debug_str/line_str objects DWARF5    FAILED (debugedit.at:129)
>   9: debugedit .debug_info objects                   FAILED (debugedit.at:291)
>  12: debugedit .debug_types objects                  FAILED (debugedit.at:370)
>  15: debugedit .debug_line objects DWARF4            FAILED (debugedit.at:460)
>  16: debugedit .debug_line objects DWARF5            FAILED (debugedit.at:484)
>  21: debugedit .debug_macro objects                  FAILED (debugedit.at:598)
> 
> Fix this by instructing gcc not to produce compressed debug sections
> in object files prepared for debugedit tests.
> 
> * tests/debugedit.at: Add "-gz=none" to "gcc -g3" invocations.

Yes, that is a good workaround for now.
But we should at least give a good error message.
And ideally just handle compressed debug ELF sections (But then the
question is how? Do we always simply decompress, do we require an
explicit command line option? Do we simply recompress when done?)

I filed https://sourceware.org/bugzilla/show_bug.cgi?id=27636

> Co-authored-by: Vitaly Chikunov <vt@altlinux.org>

And Signed-off-by: Dmitry V. Levin <ldv@altlinux.org>, I assume?

Thanks,

Mark


More information about the Debugedit mailing list