Date: Tue, 05 Sep 2023 20:59:12 +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@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D273585 Bug ID: 273585 Summary: walk_cb_call() prints warning polluting program output Product: Base System Version: 13.2-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: misc Assignee: bugs@FreeBSD.org Reporter: mkrzewicki@gmail.com walk_cb_call() from /lib/libc/stdlib/cxa_thread_atexit_impl.c=20 prints a warning at thread exit if the library that registered the action no longer can be found, no further action is taken, the dtor is then skipped. The additional output to stderr pollutes the output of binaries checked by = e.g. ctest, throwing the test suite off. In my case the program is root (CERN's data analysis suite) which features a C++ interpreter and does a lot of internal lib loading/unloading. My question is: is this behaviour absolutely required? Or could the printou= t be made optional; as in only there in some debug mode, or possibly steered by = an env variable? Patching libc may work for me for now, but would be harder to justify in a larger prod environment. thanks, Mikolaj --=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>