Date: Thu, 07 Sep 2023 01:34:36 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 273585] walk_cb_call() prints warning polluting program output Message-ID: <bug-273585-227-Scb0pfu5ne@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-273585-227@https.bugs.freebsd.org/bugzilla/> References: <bug-273585-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D273585 Ed Maste <emaste@freebsd.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |emaste@freebsd.org --- Comment #1 from Ed Maste <emaste@freebsd.org> --- The diagnostic output came from the initial introduction of __cxa_thread_at= exit in b585cd3e2c7f. The commit message notes: > - how to handle destructors which belong to an unloading dso; > for now, we ignore destructor calls for such entries, and > issue a diagnostic. Linux does prevent dso unload until all > threads with destructors from the dso terminated. > It is supposed that the diagnostics allow to detect real-world > applications relying on the above details and possibly adjust > our implementation. Right now the choices were to provide the slim > API (but that rarely stands the practice test). If this same software running on Linux would prevent the dso from being unloaded then this is a pretty significant behavioural difference, and the diagnostic message is useful in prompting this PR and resulting discussion. It would be good to have confirmation of how this software behaves on Linux; perhaps dlclose() is returning an error there that is just silently ignored? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-273585-227-Scb0pfu5ne>