From owner-freebsd-toolchain@FreeBSD.ORG  Thu Feb 20 17:24:55 2014
Return-Path: <owner-freebsd-toolchain@FreeBSD.ORG>
Delivered-To: freebsd-toolchain@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 5FC7F55A;
 Thu, 20 Feb 2014 17:24:55 +0000 (UTC)
Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 2B9A5195B;
 Thu, 20 Feb 2014 17:24:54 +0000 (UTC)
Received: from [192.168.0.7] (cpc28-cmbg15-2-0-cust64.5-4.cable.virginm.net
 [86.27.189.65]) (authenticated bits=0)
 by theravensnest.org (8.14.7/8.14.5) with ESMTP id s1KHOXdN017461
 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
 Thu, 20 Feb 2014 17:24:42 GMT (envelope-from theraven@FreeBSD.org)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: ctfconvert broken for C++ objects?
From: David Chisnall <theraven@FreeBSD.org>
In-Reply-To: <216B816A-8ADA-438F-B834-8C386C5BC460@FreeBSD.org>
Date: Thu, 20 Feb 2014 17:24:18 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <B818D452-280F-4AA1-9F7D-298C384F3868@FreeBSD.org>
References: <216B816A-8ADA-438F-B834-8C386C5BC460@FreeBSD.org>
To: "Justin T. Gibbs" <gibbs@FreeBSD.org>
X-Mailer: Apple Mail (2.1827)
Cc: freebsd-toolchain@freebsd.org
X-BeenThere: freebsd-toolchain@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Maintenance of FreeBSD's integrated toolchain
 <freebsd-toolchain.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-toolchain>, 
 <mailto:freebsd-toolchain-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-toolchain/>
List-Post: <mailto:freebsd-toolchain@freebsd.org>
List-Help: <mailto:freebsd-toolchain-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-toolchain>, 
 <mailto:freebsd-toolchain-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Feb 2014 17:24:55 -0000

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. =20

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 =93PROG_CXX=94 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=92m hoping someone here with =
more dwarf experience can point me in the right direction for a real =
fix.  Is this a known issue?
>=20
> I=92m testing this on a FreeBSD stable/9 from ~November of last year.
>=20
> Thanks,
> Justin
>=20
> <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"