From owner-freebsd-current@FreeBSD.ORG  Mon Dec 10 22:06:20 2012
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 A3D336C
 for <freebsd-current@freebsd.org>; Mon, 10 Dec 2012 22:06:20 +0000 (UTC)
 (envelope-from rysto32@gmail.com)
Received: from mail-vb0-f54.google.com (mail-vb0-f54.google.com
 [209.85.212.54])
 by mx1.freebsd.org (Postfix) with ESMTP id 4D1918FC08
 for <freebsd-current@freebsd.org>; Mon, 10 Dec 2012 22:06:20 +0000 (UTC)
Received: by mail-vb0-f54.google.com with SMTP id l1so3931310vba.13
 for <freebsd-current@freebsd.org>; Mon, 10 Dec 2012 14:06:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type;
 bh=x7SxpJZnNx4AukYuUPmh9M0Yvqmhg9LUhBNL9/gL094=;
 b=lqhhGhUF2MB/5cLFnmAbAMun9v7EwoxdOX55y9Loa68ZaFneNcchQ+T/u8mdKIpv6m
 gD0IlLRw+JWLWq5BxZHIF9y8KuWZOvkSsa1WfdLb3m/WZ4CX7/lkmYNFiAdqsfiJWZlq
 hRoGFAZo/8mho/HILuWMEyOZfGxp9qpfSFzzt1dR1QQYIfEcKws/ZdPIpZujAjreeRcy
 oZxKklgcvUNpK8smq/o1egotohSdxyoiN3lrOYN0zzxVJerCLC9BjKBPNzHXp/U7ZzgF
 YcjkEZ7K5JDxoD4zqf/JzM6ITwen+wITSr/drtI0Xt45GTbciGVBxXxH6jZXsVSU3bDm
 9quQ==
MIME-Version: 1.0
Received: by 10.58.240.107 with SMTP id vz11mr10148478vec.45.1355177179725;
 Mon, 10 Dec 2012 14:06:19 -0800 (PST)
Received: by 10.58.207.114 with HTTP; Mon, 10 Dec 2012 14:06:19 -0800 (PST)
In-Reply-To: <ka56gv$t60$1@ger.gmane.org>
References: <k9qjml$ri7$1@ger.gmane.org> <50C1E81A.1040107@FreeBSD.org>
 <50C1F862.2010501@FreeBSD.org> <k9t6bq$bhs$1@ger.gmane.org>
 <50C22789.3030303@FreeBSD.org> <ka56gv$t60$1@ger.gmane.org>
Date: Mon, 10 Dec 2012 17:06:19 -0500
Message-ID: <CAFMmRNw7gROHdtc54wMqsZ820cMdcCNcY9kmwqNeYfotKzGhcQ@mail.gmail.com>
Subject: Re: problems with threads/destructors in -current with llvm/clang
From: Ryan Stone <rysto32@gmail.com>
To: Mark Atkinson <atkin901@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Content-Filtered-By: Mailman/MimeDel 2.1.14
Cc: FreeBSD Current <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
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Dec 2012 22:06:20 -0000

On Mon, Dec 10, 2012 at 12:35 PM, Mark Atkinson <atkin901@gmail.com> wrote:

> vex x86->IR: unhandled instruction bytes: 0xF 0xB 0x90 0x90
> ==33074== valgrind: Unrecognised instruction at address 0x380434e9.
> ==33074==    at 0x380434E9: ??? (in
> /usr/local/lib/valgrind/memcheck-x86-freebsd)
> ==33074==    by 0x323C48: qt_safe_select(int, fd_set*, fd_set*,
> fd_set*, timeval const*) (qcore_unix.cpp:83)
> ==33074==    by 0x2803B1: select_msecs(int, fd_set*, fd_set*, int)
> (qprocess_unix.cpp:998)
> ==33074==    by 0x28021D: QProcessPrivate::waitForStarted(int)
> (qprocess_unix.cpp:1031)
> ==33074==    by 0x1FFA02: QProcess::waitForStarted(int)
> (qprocess.cpp:1687)
> ==33074==    by 0x1FEAEA: QProcess::waitForFinished(int)
> (qprocess.cpp:1752)
> ==33074==    by 0x805487A: AutoMoc::echoColor(QString const&)
> (kde4automoc.cpp:74)
> ==33074==    by 0x805264F: AutoMoc::generateMoc(QString const&,
> QString const&) (kde4automoc.cpp:569)
> ==33074==    by 0x804F13A: AutoMoc::run() (kde4automoc.cpp:470)
> ==33074==    by 0x804AAEE: main (kde4automoc.cpp:114)
>
> Full valgrind output is at http://pastebin.com/KQTKYGX5
>

This sounds like a valgrind bug I reported related to sigreturn:

https://bitbucket.org/stass/valgrind-freebsd/issue/4/crash-in-x86_freebsd_subst_for_sigreturn

Unfortunately I don't understand the mechanics of signal handling well
enough to take this to completion.