https://bugs.kde.org/show_bug.cgi?id=421931
--- Comment #2 from Carlos O'Donell <car...@redhat.com> --- (In reply to Mark Wielaard from comment #1) > Which process shutdown steps do you expect to run during or after > __libc_freeres is called? Any detached thread may write to the stream until the kernel kills the task. > __libc_freeres as used by valgrind should be the last "user code" running, > no other threads should be scheduled. It is called after all user threads > are "dead". And after __libc_freeres has ran only the valgrind (tool) code > will run (which doesn't use glibc code). How do you wait for detached threads? > So at least from the perspective of valgrind __libc_freeres can release all > resources. So from your perspective at this point, even detached threads, can expect to have the streams shutdown? -- You are receiving this mail because: You are watching all bug changes.
