Hello,
On Tue, 23 Aug 2022, Florian Weimer via Gcc wrote:
> We currently have a latent bug in glibc where C++ constructor calls can
> fail if they have static or thread storage duration and a non-trivial
> destructor. The reason is that __cxa_atexit (and
> __cxa_thread_atexit_impl) may have to a
Hi Florian,
What would be the most ELF-flavored way to implement this? After the
final link, I expect that the count (or counts, we need a separate
counter for thread-local storage) would show up under a new dynamic tag
in the dynamic segment. This is actually a very good fit because older
loa
We currently have a latent bug in glibc where C++ constructor calls can
fail if they have static or thread storage duration and a non-trivial
destructor. The reason is that __cxa_atexit (and
__cxa_thread_atexit_impl) may have to allocate memory. We can avoid
that if we know how many such static c
