From: David Mosberger <davidm@napali.hpl.hp.com>
To: "H. J. Lu" <hjl@lucon.org>
Cc: davidm@hpl.hp.com, Roland McGrath <roland@frob.com>,
libc-hacker@sources.redhat.com
Subject: Re: patch to make init_array work (3nd version)
Date: Wed, 27 Nov 2002 15:34:00 -0000 [thread overview]
Message-ID: <15845.22139.286152.270593@napali.hpl.hp.com> (raw)
In-Reply-To: <20021127150958.A15921@lucon.org>
>>>>> On Wed, 27 Nov 2002 15:09:58 -0800, "H. J. Lu" <hjl@lucon.org> said:
HJ> I am not sure how this approach will work. If I get it right,
HJ> __libc_do_init_calls and __libc_do_fini_calls are defined in
HJ> executables. But they are only available when executables are
HJ> linked against with the new glibc. For the existing executables,
HJ> there are no __libc_do_init_calls nor __libc_do_fini_calls. That
HJ> is why my original solution has
Old executables directly pass _init() and _fini() to
__libc_start_main, so they'll work normally. Of course, the
preinit_array, init_array, and fini_array in such executables won't be
executed either, but since this support is new, those binaries
presumably don't have such sections. Also, ld.so should take care of
executing init_array and fini_array for the shared objects that the
executable depends on, so I think everything should be fine.
--david
next prev parent reply other threads:[~2002-11-27 23:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-08 11:34 patch to make init_array work (2nd version; resend) Roland McGrath
2002-11-08 11:38 ` David Mosberger
2002-11-27 14:35 ` patch to make init_array work (3nd version) David Mosberger
2002-11-27 15:10 ` H. J. Lu
2002-11-27 15:34 ` David Mosberger [this message]
2002-12-09 10:52 ` Roland McGrath
2002-12-09 13:36 ` David Mosberger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=15845.22139.286152.270593@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=davidm@hpl.hp.com \
--cc=hjl@lucon.org \
--cc=libc-hacker@sources.redhat.com \
--cc=roland@frob.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).