[Bug 273585] walk_cb_call() prints warning polluting program output
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 273585] walk_cb_call() prints warning polluting program output"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 273585] walk_cb_call() prints warning polluting program output"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 273585] walk_cb_call() prints warning polluting program output"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Tue, 05 Sep 2023 20:59:12 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273585
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
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 printout 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
--
You are receiving this mail because:
You are the assignee for the bug.