Date: Mon, 27 Jul 2020 21:28:31 +0200 From: Paul Floyd <pjfloyd@wanadoo.fr> To: toolchain@freebsd.org Subject: Re: Getting started with clang debuginfo Message-ID: <9068E247-2FCA-4CCD-86E0-F715C0057EED@wanadoo.fr> In-Reply-To: <20200727143753.GA59953@raichu> References: <1139268534.2282.1595842060133.JavaMail.www@wwinf1m22> <20200727143753.GA59953@raichu>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 27 Jul 2020, at 16:37, Mark Johnston <markj@freebsd.org> wrote: >=20 > On Mon, Jul 27, 2020 at 11:27:40AM +0200, Paul FLOYD wrote: >> Hi >> =20 >> I'm investigating some of the remaining issues with Valgrind on = FreeBSD. One of the two remaining major issues that I'm aware of is with = Valgrind reading dwarf debuginfo from clang compiled binaries. The = problem isn't too bad with clang 8 on FreeBSD 12.1. On 13-CURRENT with = clang 10 things are noticeably worse. For GCC built binaries I'm not = aware of any issues. >> =20 >> I'm not familiar (yet) with the debuginfo code in Valgrind. >> =20 >> To get me going, does anyone have any pointers to >> - documentation on clang debuginfo >> - any info on differences wrt GCC (I have seen that GCC does have = some debuginfo extensions) >> - any tools that would be useful like ascii dumps >=20 > Are you asking about tools to dump DWARF info? I've used dwarfdump > (from ports) quite a bit in the past. readelf -w is similar and > available in the base system. Hi Mark Yes, I=E2=80=99m trying to start working out where there are differences Clang 8 vs clang 10 vs just about any GCC I=E2=80=99d already seen readelf, but I hadn=E2=80=99t installed = dwarfdump. I just had a look at one example, there=E2=80=99s a bit less info in the = clang generated file, but otherwise it looks OK. Next I=E2=80=99ll try comparing a problem clang 10 binary with a clang 8 = one. A+ Paul
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9068E247-2FCA-4CCD-86E0-F715C0057EED>