From owner-freebsd-current@FreeBSD.ORG Fri Dec 7 17:29:44 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0A5E1728 for ; Fri, 7 Dec 2012 17:29:44 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) by mx1.freebsd.org (Postfix) with ESMTP id AF1F18FC08 for ; Fri, 7 Dec 2012 17:29:43 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7:0:7cf2:29c9:3fd9:2525] (unknown [IPv6:2001:7b8:3a7:0:7cf2:29c9:3fd9:2525]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 527905C37; Fri, 7 Dec 2012 18:29:42 +0100 (CET) Message-ID: <50C22789.3030303@FreeBSD.org> Date: Fri, 07 Dec 2012 18:29:45 +0100 From: Dimitry Andric Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:18.0) Gecko/20121128 Thunderbird/18.0 MIME-Version: 1.0 To: Mark Atkinson Subject: Re: problems with threads/destructors in -current with llvm/clang References: <50C1E81A.1040107@FreeBSD.org> <50C1F862.2010501@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, kde-freebsd@freebsd.kde.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Dec 2012 17:29:44 -0000 On 2012-12-07 17:43, Mark Atkinson wrote: > On 12/7/2012 6:08 AM, Dimitry Andric wrote: ... >> With this patch (placed in /usr/ports/devel/dbus-qt4/files), qdbus >> starts up and exits normally for me. I did not do any other rigorous >> testing, though. :) > > Thanks for the awesome analysis. I will endeavor to figure out the bug > in automoc4 that keeps it segfaulting randomly during compilation. > > Weirdly it segfaults reliably under portmaster, but may work just fine > under just make. Try running it under valgrind. If it does undefined things, it may work or not work randomly, and valgrind usually catches this.