From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Richard Henderson <rth@twiddle.net>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Shared Library starter, ld.so
Date: Fri, 6 Jun 2003 07:34:50 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.53.0306060721400.4852@chaos> (raw)
In-Reply-To: <20030606101313.GA28939@twiddle.net>
On Fri, 6 Jun 2003, Richard Henderson wrote:
> On Thu, Jun 05, 2003 at 10:46:18AM -0400, Richard B. Johnson wrote:
> > The dynamic linker, provided with RedHat 9 no longer
> > compiles with the de facto standard of having register
> > EDX point to function to be called before exit.
>
> You're wrong. Indeed, the rh9 crt1.o still expects the value:
>
>
> 8: 50 push %eax
> 9: 54 push %esp
> a: 52 push %edx <<==== HERE
> b: 68 00 00 00 00 push $0x0
> c: R_386_32 __libc_csu_fini
> 10: 68 00 00 00 00 push $0x0
> 11: R_386_32 __libc_csu_init
> 15: 51 push %ecx
> 16: 56 push %esi
> 17: 68 00 00 00 00 push $0x0
> 18: R_386_32 main
> 1c: e8 fc ff ff ff call 1d <_start+0x1d>
> 1d: R_386_PC32 __libc_start_main
>
> and ld.so provides the value here:
>
> # Pass our finalizer function to the user in %edx, as per ELF ABI.\n\
> leal _dl_fini@GOTOFF(%ebx), %edx\n\
>
I am NOT wrong. I have crt startup code and if you actually CALL
the value in %edx, you __will__ segfault. So do a bit of research
before you claim that I'm wrong. Newer versions of the 'C' runtime
library simply fail to call that pointer in atexit(), before exit()
is called.
These things are so easily checked. Just assemble and link this code
against your favorite shared library.
#
# This is the entry point, usually the first thing in the text
# segment. The SVR4/i386 ABI (pages 3-31, 3-32) says that upon
# entry most registers' values are unspecified, except for:
#
# %edx Contains a function pointer to be registered with `atexit'.
# This is how the dynamic linker arranges to have DT_FINI
# functions called for shared libraries that have been loaded
# before this code runs.
#
# %esp The stack contains the arguments and environment:
# 0(%esp) argc
# 4(%esp) argv[0]
# ...
# (4*argc)(%esp) NULL
# (4*(argc+1))(%esp) envp[0]
# ...
# NULL
#
.section .text
.global _start
.type _start,@function
_start: call *%edx
pushl $0
call exit
.end
It works, i.e., exits without any errors with the ld-linux.so that
exists on all my systems except the Red Hat 9 system.
On the Red Hat 9 system, it will segfault.
Cheers,
Dick Johnson
Penguin : Linux version 2.4.20 on an i686 machine (797.90 BogoMips).
Why is the government concerned about the lunatic fringe? Think about it.
next prev parent reply other threads:[~2003-06-06 11:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-05 14:46 Richard B. Johnson
2003-06-06 10:13 ` Richard Henderson
2003-06-06 11:34 ` Richard B. Johnson [this message]
2003-06-06 21:10 ` Richard Henderson
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=Pine.LNX.4.53.0306060721400.4852@chaos \
--to=root@chaos.analogic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rth@twiddle.net \
/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
all inboxes | Powered by JetHome®