https://bugs.kde.org/show_bug.cgi?id=306340
Mark Wielaard <m...@klomp.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |NOT A BUG
Status|REPORTED |RESOLVED
--- Comment #7 from Mark Wielaard <m...@klomp.org> ---
The llvm bug is still open https://github.com/llvm/llvm-project/issues/13723
but I think it might have been fixed since we haven't seen this issue in a very
long time.
sgcheck isn't part of valgrind anymore. But you can still trigger this with
valgrind 3.21.0 using --read-var-info=yes:
$ valgrind --read-var-info=yes /tmp/frob
==8280== Memcheck, a memory error detector
==8280== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
==8280== Using Valgrind-3.21.0 and LibVEX; rerun with -h for copyright info
==8280== Command: /tmp/frob
==8280==
parse DIE(readdwarf3.c:3025): confused by:
<0><10d>: Abbrev Number: 1 (DW_TAG_compile_unit)
DW_AT_producer : (indirect string, offset: 0xab): clang version 3.1
(branches/release_31)
DW_AT_language : 12
DW_AT_name : (indirect string, offset: 0xd3): ../a.c
DW_AT_low_pc : 0x0
DW_AT_stmt_list : 136
DW_AT_comp_dir : (indirect string, offset: 0xda): /home/uabpath/tmp
parse_var_DIE:
--8280-- WARNING: Serious error when reading debug info
--8280-- When reading debug info from /tmp/frob:
--8280-- confused by the above DIE
It won't trigger for valgrind 3.22.0 since that has lazy debuginfo reading by
default and since the debuginfo isn't actually needed it won't parse it...
Since this is just a warning and a real bug in llvm produced debuginfo I am
closing this bug.
--
You are receiving this mail because:
You are watching all bug changes.
