Date: Fri, 9 Feb 2024 21:15:06 +0100 From: Paul Floyd <pjfloyd@wanadoo.fr> To: toolchain@FreeBSD.org Subject: debuginfo changes Message-ID: <33b63792-0311-4f71-b75d-ba12b51510a7@wanadoo.fr>
next in thread | raw e-mail | index | archive | help
Hi
I recently upgraded from FreeBSD 13.2 to 14.0 amd64.
I'm getting one new Valgrind regression test failure that seems to be
related to DWARF debuginfo.
The changes are partly better, partly worse.
Here is an example from the diff
Uninitialised byte(s) found during client check request
at 0x........: croak (tests/varinfo5so.c:29)
- by 0x........: bar3 (tests/varinfo5so.c:97)
by 0x........: foo3 (tests/varinfo5so.c:110)
- by 0x........: varinfo3_main (tests/varinfo5so.c:118)
by 0x........: varinfo5_main (tests/varinfo5so.c:156)
by 0x........: main (tests/varinfo5.c:5)
- Address 0x........ is on thread 1's stack
- in frame #X, created by foo3 (varinfo5so.c:101)
+ Location 0x........ is 0 bytes inside nonstatic_local_undef[8],
+ declared at varinfo5so.c:105, in frame #X of thread 1
The good bit it at the end. Valgrind has found the variable name
rather than just saying it is on the stack.
The bad bit is the missing lines in the callstack. They are due to
inline functions.
Does anyone have any information as to what might have changed between
clang 14.0.5 and 16.0.6?
A+
Paul
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?33b63792-0311-4f71-b75d-ba12b51510a7>