Date: Thu, 20 Feb 2014 17:24:18 +0000 From: David Chisnall <theraven@FreeBSD.org> To: "Justin T. Gibbs" <gibbs@FreeBSD.org> Cc: freebsd-toolchain@freebsd.org Subject: Re: ctfconvert broken for C++ objects? Message-ID: <B818D452-280F-4AA1-9F7D-298C384F3868@FreeBSD.org> In-Reply-To: <216B816A-8ADA-438F-B834-8C386C5BC460@FreeBSD.org> References: <216B816A-8ADA-438F-B834-8C386C5BC460@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
We're likely to keep hitting these. Ideally, we should replace the libdwarf usage in ctfconvert with either the LLVM or LLDB dwarf parsing, which is getting to be quite mature now and can handle complex encodings. The DWARF5 spec is due out this year and LLVM is already implementing (disabled by default) several of the proposed extensions to DWARF4 that are likely to make it into DWARF5. David On 20 Feb 2014, at 00:16, Justin T. Gibbs <gibbs@FreeBSD.org> wrote: > I noticed that ctfmerge was warning about missing CTF data when compiling “PROG_CXX” programs. I tracked this down to missing ctfconvert calls when compiling C++ objects. Unfortunately, ctfconvert segfaults in libdwarf on all of the C++ code I tried. Attached is a quick hack to avoid the segfault, but I’m hoping someone here with more dwarf experience can point me in the right direction for a real fix. Is this a known issue? > > I’m testing this on a FreeBSD stable/9 from ~November of last year. > > Thanks, > Justin > > <ctf_for_c++.diffs>_______________________________________________ > freebsd-toolchain@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-toolchain > To unsubscribe, send any mail to "freebsd-toolchain-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B818D452-280F-4AA1-9F7D-298C384F3868>