This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
Re: when will __attribute__((constructor)) NOT called
- From: Adhemerval Zanella <adhemerval dot zanella at linaro dot org>
- To: libc-help at sourceware dot org
- Date: Wed, 6 Sep 2017 09:46:33 -0300
- Subject: Re: when will __attribute__((constructor)) NOT called
- Authentication-results: sourceware.org; auth=none
- References: <CAJYFCiNBRzwzuNcaFjuswT+PCx61bygwa=Q9+jtShG3nzNu1uw@mail.gmail.com>
'.ctor' section was the 'old' way, afaik GCC will now create and emit
entries on 'init_array' section, as for C++ initialization code.
It won't run either by a bug on the loader or if it does not support
it (not the case on glibc).
On 06/09/2017 07:37, Yubin Ruan wrote:
> I saw somewhere that "__attribute__((constructor)) will make GCC
> create a '.ctor' section in the generated .so file, which is run when
> a shared library is loaded, typically at program startup".
>
> A question:
> Are there any case where "__attribute__((constructor))" will not be run?
>
> Thanks,
> Yubin
>