Re: __cxa_thread_call_dtors: dtr 0x........ from unloaded dso, skipping
Date: Tue, 11 Feb 2025 02:06:13 UTC
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 <bzeeb-lists@lists.zabbadoz.net> wrote:
> > >
> > > On Mon, 26 Jun 2023, Dimitry Andric wrote:
> > >
> > > > On 26 Jun 2023, at 17:00, Bjoern A. Zeeb <bzeeb-lists@lists.zabbadoz.net> 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.