From: Roland McGrath <roland@frob.com>
To: Geoff Keating <geoffk@ozemail.com.au>
Cc: drepper@cygnus.com, libc-hacker@sourceware.cygnus.com
Subject: Re: more ELF changes
Date: Sun, 25 Jul 1999 09:53:00 -0000 [thread overview]
Message-ID: <199907251653.MAA00807@frob.com> (raw)
In-Reply-To: <199907251349.XAA00772@geoffk.wattle.id.au>
> My suggestion would be to do it in _dl_start. Pass all init functions
> argc, argv, and envp. This is what dlopen does anyway, so there is no
> point trying to do anything tricky in the startup code, because it
> won't work properly when the library is dlopen()ed (and we don't in
> fact do anything tricky now, anyway).
We do do something tricky in libc on the Hurd.
See sysdeps/mach/hurd/i386/init-first.c; it switches stacks.
It's not reasonable for DT_INIT functions in general to do tricky things,
because they might be run via dlopen. But libc itself reasonably expects
always to be the first library initialized, and so it can do tricky things.
prev parent reply other threads:[~1999-07-25 9:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-24 15:20 Ulrich Drepper
1999-07-24 15:59 ` Roland McGrath
1999-07-24 17:28 ` Ulrich Drepper
1999-07-25 6:50 ` Geoff Keating
1999-07-25 9:53 ` Roland McGrath [this message]
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=199907251653.MAA00807@frob.com \
--to=roland@frob.com \
--cc=drepper@cygnus.com \
--cc=geoffk@ozemail.com.au \
--cc=libc-hacker@sourceware.cygnus.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).