From nobody Tue Feb 11 02:06:13 2025 X-Original-To: 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 4YsPvD1Yl0z5nCXt for ; Tue, 11 Feb 2025 02:06:32 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4YsPvC40kRz3sT4; Tue, 11 Feb 2025 02:06:31 +0000 (UTC) (envelope-from kostikbel@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: from tom.home (kib@localhost [127.0.0.1] (may be forged)) by kib.kiev.ua (8.18.1/8.18.1) with ESMTP id 51B26D4V078625; Tue, 11 Feb 2025 04:06:16 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua 51B26D4V078625 Received: (from kostik@localhost) by tom.home (8.18.1/8.18.1/Submit) id 51B26DNt078624; Tue, 11 Feb 2025 04:06:13 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Tue, 11 Feb 2025 04:06:13 +0200 From: Konstantin Belousov To: "Bjoern A. Zeeb" Cc: Dimitry Andric , current@freebsd.org Subject: Re: __cxa_thread_call_dtors: dtr 0x........ from unloaded dso, skipping Message-ID: References: <46pq4r4n-p46r-47nn-r1ss-7r2984891pn7@yvfgf.mnoonqbm.arg> <16A8852E-DEA9-408E-80BC-94322FB2415E@FreeBSD.org> <0A55614E-3577-4933-9CCD-4D723DFA86E8@FreeBSD.org> <4so13o96-5r39-15oo-qp05-78n11qsr2556@yvfgf.mnoonqbm.arg> 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 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4so13o96-5r39-15oo-qp05-78n11qsr2556@yvfgf.mnoonqbm.arg> X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FREEMAIL_FROM, NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=4.0.1 X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-26) on tom.home X-Rspamd-Queue-Id: 4YsPvC40kRz3sT4 X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US] On Tue, Feb 11, 2025 at 12:21:29AM +0000, Bjoern A. Zeeb wrote: > On Mon, 26 Jun 2023, Dimitry Andric wrote: > > > On 26 Jun 2023, at 17:29, Bjoern A. Zeeb wrote: > > > > > > On Mon, 26 Jun 2023, Dimitry Andric wrote: > > > > > > > On 26 Jun 2023, at 17:00, Bjoern A. Zeeb wrote: > > > > > > > > > > while building world and current I see a lot of: > > > > > > > > > > __cxa_thread_call_dtors: dtr 0x...... from unloaded dso, skipping > > > > > > > > > > Can anyone shed light on that? > > > > > > > > You need (thanks to Kostik): > > > > https://cgit.freebsd.org/src/commit/?id=42ceab3ea1a997db93b65404be0ee4b17b5382d7 > > > > > > > > Build libc and install it, then the messages should disappear. > > > > > > Great! Basically update world and it'll go. > > > Do we add an UPDATING note for this or do we consider it developer noise? > > > > I think the message has been there for a long time, but was not often > > noticed. It happened when the buildworld bootstrap decides to build a > > static bootstrap lld ("SYSTEM_LINKER: libclang will be built for > > bootstrapping a cross-linker"), so usually when lld's version is bumped. > > And that is because lld is one of the few threaded build tools in the > > tree. > > > > The messages themselves are harmless and can be ignored. Feel free to > > add an UPDATING note to that effect, otherwise worried users might think > > something is off. :) > > And it seems to be back after I updated to main from a few days ago: > > During make buildkernel I now see: > > ... > __cxa_thread_call_dtors: dtr 0xe67c10 from unloaded dso, skipping > __cxa_thread_call_dtors: dtr 0xe67c10 from unloaded dso, skipping > __cxa_thread_call_dtors: dtr 0xe67c10 from unloaded dso, skipping > __cxa_thread_call_dtors: dtr 0xe67c10 from unloaded dso, skipping > __cxa_thread_call_dtors: dtr 0xe67c10 from unloaded dso, skipping > __cxa_thread_call_dtors: dtr 0xe67c10 from unloaded dso, skipping > __cxa_thread_call_dtors: dtr 0xe67c10 from unloaded dso, skipping > __cxa_thread_call_dtors: dtr 0xe67c10 from unloaded dso, skipping > __cxa_thread_call_dtors: dtr 0xe67c10 from unloaded dso, skipping > __cxa_thread_call_dtors: dtr 0xe67c10 from unloaded dso, skipping > __cxa_thread_call_dtors: dtr 0xe67c10 from unloaded dso, skipping > __cxa_thread_call_dtors: dtr 0xe67c10 from unloaded dso, skipping > __cxa_thread_call_dtors: dtr 0xe67c10 from unloaded dso, skipping > __cxa_thread_call_dtors: dtr 0xe67c10 from unloaded dso, skipping > __cxa_thread_call_dtors: dtr 0xe67c10 from unloaded dso, skipping > __cxa_thread_call_dtors: dtr 0xe67c10 from unloaded dso, skipping > __cxa_thread_call_dtors: dtr 0xe67c10 from unloaded dso, skipping > __cxa_thread_call_dtors: dtr 0xe67c10 from unloaded dso, skipping > __cxa_thread_call_dtors: dtr 0xe67c10 from unloaded dso, skipping > __cxa_thread_call_dtors: dtr 0xf043d0 from unloaded dso, skipping > __cxa_thread_call_dtors: dtr 0xe7bc90 from unloaded dso, skipping > __cxa_thread_call_dtors: dtr 0xe67c10 from unloaded dso, skipping > __cxa_thread_call_dtors: dtr 0xf043d0 from unloaded dso, skipping > __cxa_thread_call_dtors: dtr 0xe7bc90 from unloaded dso, skipping > __cxa_thread_call_dtors: dtr 0xe67c10 from unloaded dso, skipping > __cxa_thread_call_dtors: dtr 0xe67c10 from unloaded dso, skipping > __cxa_thread_call_dtors: dtr 0xe67c10 from unloaded dso, skipping > __cxa_thread_call_dtors: dtr 0xe67c10 from unloaded dso, skipping > __cxa_thread_call_dtors: dtr 0xe67c10 from unloaded dso, skipping > __cxa_thread_call_dtors: dtr 0xe67c10 from unloaded dso, skipping > __cxa_thread_call_dtors: dtr 0xe67c10 from unloaded dso, skipping > __cxa_thread_call_dtors: dtr 0xe67c10 from unloaded dso, skipping > __cxa_thread_call_dtors: dtr 0xe67c10 from unloaded dso, skipping > ... Your linker is old. I believe this should cure itself after the upgrade is done.