From nobody Thu Nov 21 17:27:36 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4XvQCv0P7rz5dMrS; Thu, 21 Nov 2024 17:27:39 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XvQCt6vZxz4RCD; Thu, 21 Nov 2024 17:27:38 +0000 (UTC) (envelope-from dim@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1732210059; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=oZGndYgjb7SXxzpGUuG2mFFU7Yxh9UrcfW+vV72JdE0=; b=HY6aP2ZcoiUlxMYu037nvzDUHzK2WlXcfH4aWG+gYSkKmLRF3/BhCurlXvT+Zn31cDdyUb ttCvGvy+/nlzqI6gtENUZxEeAjSf2pUAXNejyNof/sFCZdXKK8BtbEaEIBrMWV4wgLsvv8 BTS+qtCIPncn7WjZiOxZb0UKHQ4PeN43rcpg45U2w/4zepUgvwjHeAhknu3Y9R20tqk/Wj YFGa+CNz69xEsIfZpl3sc+keUKLIzIYyz7Vk3Ji3Byf/wTAv8cUFl0t9MQaD55ys6bi3ZZ FMeRCR+bvnPko+CSuQCKTcXDkmLv0D2Es46R/fTrATS3leU9S3SZgK2JdQtjZw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1732210059; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=oZGndYgjb7SXxzpGUuG2mFFU7Yxh9UrcfW+vV72JdE0=; b=Hjx4nJQZtlbvAwI2BNIVvIazLerZ+9H9xEuG9p9oF+CVLUPyyF8dXPQlaWASSJLOYD9LOZ tR0Q8IVS4eKTSUqKc/vmJX3jrI25/gqjWwWY+jZ0D9dNOOrH5ViRtbHK2grue8XQK6udN5 uZS+wgYWFFoGqd6JNbx/lYVT716ZRu5tyl81peYJXo5a1ZEZqTGGE+iYXK1rcFbagh0Eag w5ODQunZE4ZxB+mjDmbiEwWxyxpaEMtzw+e5TjpJ4VgERLlEBc4rFeUSCtMdx8OnWp8QX5 OW4QDb+43r9nt9aB5hPR9qAGqi2EH2jEQ8ewRBFe6JkbUxnnhkFvNQfmTHrz2Q== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1732210059; a=rsa-sha256; cv=none; b=st1pzZNRrl/cQiU61YDvWLA9xSR2pOVLRBCQDBA/fu7NfQYMvMTeF4rXm/+C35ghiJ00v/ x6Mig8tNGF+GHj0np350AyyfRicOnChbKGs+O0BGeJAT3Ybt3+zoHjw68BW5360SuPNR6w MAn+a8zd2cKB6H5o7rJUXTem3IVyGpjEleiJIsn1QQjXn7NtIg+SvyJY6xkSyj/eYBZ96s sfDuG2BeKislH+d/ylyjnAHGexQMva89X4OQWyF/f6nlXFI9f6qe7/l5/37hD6bg8EFRBv 97KlbRBymsqo7o4qFF13ZkBgKzGocabTQxbI88rDMuTUqhmXd4wpWBNdQ6uRBA== Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "tensor.andric.com", Issuer "R10" (verified OK)) (Authenticated sender: dim) by smtp.freebsd.org (Postfix) with ESMTPSA id 4XvQCt5mVPzRhM; Thu, 21 Nov 2024 17:27:38 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from smtpclient.apple (longrow.home.andric.com [192.168.0.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 24E8A2ED13; Thu, 21 Nov 2024 18:27:37 +0100 (CET) Content-Type: text/plain; charset=us-ascii List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6.1.9\)) Subject: Re: port binary dumping core on recent head in poudriere From: Dimitry Andric In-Reply-To: Date: Thu, 21 Nov 2024 18:27:36 +0100 Cc: ports@freebsd.org, FreeBSD Current Content-Transfer-Encoding: quoted-printable Message-Id: References: <46E3A370-A3E0-4BAF-B707-87F94F98E248@FreeBSD.org> <5ee47c3d-f80e-4d50-9b6a-acb3c98e80e0@madpilot.net> To: Guido Falsi X-Mailer: Apple Mail (2.3731.700.6.1.9) On 21 Nov 2024, at 18:17, Guido Falsi wrote: >=20 > On 20/11/24 23:50, Guido Falsi wrote: >> On 20/11/24 22:14, Dimitry Andric wrote: >>> On 20 Nov 2024, at 18:32, Guido Falsi wrote: >>>> I've noticed that recently some ports are dumping core during = builds of dependencies in head in poudriere. >>>>=20 >>>> I'm seeing this for example with sassc crashing while trying to = build x11-themes/greybird-theme. >>>>=20 >>>> My first suspect was the llvm upgrade in head, but forcing sassc = and libsass to build with older clang via USES=3Dllvm:max=3D18 is not = helping. >>>>=20 >>>> I did recompile the offending programs with debug and tried a = backtrace and got this: >>>>=20 >>>> ``` >>>> (lldb) bt >>>> * thread #1, name =3D 'sassc', stop reason =3D signal SIGSEGV: = invalid permissions for mapped object (fault address: 0x82374a000) >>>> * frame #0: 0x000000082374a000 libsass.so.1 >>>> frame #1: 0x0000000823865a86 = libsass.so.1`_GLOBAL__sub_I_ast.cpp [inlined] double = std::__1::__math::acos[abi:se190102](__x=3D-1) at = inverse_trigonometric_functions.h:40:10 >>>> frame #2: 0x0000000823865a81 = libsass.so.1`_GLOBAL__sub_I_ast.cpp [inlined] __cxx_global_var_init at = units.hpp:11:21 >>>> frame #3: 0x0000000823865a81 = libsass.so.1`_GLOBAL__sub_I_ast.cpp at ast.cpp:0 >>>> frame #4: 0x00001eac6e3f078d ld-elf.so.1 >>>> frame #5: 0x00001eac6e3ef349 ld-elf.so.1 >>>> frame #6: 0x00001eac6e3ec099 = ld-elf.so.1`___lldb_unnamed_symbol27 + 25 >>>> ``` >>>>=20 >>>> which points me to this upstream line of code: https://github.com/ = sass/libsass/blob/7037f03fabeb2b18b5efa84403f5a6d7a990f460/src/ = units.hpp#L11 >>>>=20 >>>> I could change the way it derives PI, but I'm not sure this is the = correct fix. >>>=20 >>> At first sight this looks like some sort of initialization order = fiasco, but without a full backtrace and some indications on what it is = exactly segfaulting on it is hard to say. Is it reproducible? >> It is fully reproducible here by just compiling the sassc port and = trying to run it. It segfaults on startup. >=20 > I'm following up to myself to note that I'm observing the same issue = in textproc/opensp if trying to run anything linked with the library, = for example its own binary "osx". >=20 > I noticed it because it is required by libosp and then by gnucash = which I use and maintain. libosp fails during configure due to a test = binary compiled by configure script dumping core. >=20 > I suspect there are more around the ports tree. I cannot reproduce this at all. For me the sassc binary runs fine, and = also the x11-themes/greybird-theme port builds fine. Then again, my base = system is probably older than yours? Which revision are you running? -Dimitry