From: "David S. Miller" <davem@davemloft.net>
To: libc-hacker@sources.redhat.com
Subject: Re: weird versioning crash...
Date: Wed, 29 Mar 2006 01:46:00 -0000 [thread overview]
Message-ID: <20060328.174701.11633966.davem@davemloft.net> (raw)
In-Reply-To: <20060328.162324.107326686.davem@davemloft.net>
From: "David S. Miller" <davem@davemloft.net>
Date: Tue, 28 Mar 2006 16:23:24 -0800 (PST)
> The "ndx" VERSYM entry for _etext is "0xa822", which is 0x2822 with
> the "hidden" 0x8000 bit masked out. That is way out of range.
>
> Sometimes things work because something happens to be mapped at that
> offset from the map->l_versions[] table.
>
> What I can't figure out is if that bogus hidden _etext entry is there
> due to a binutils bug, or perhaps bad arguments given to the link of
> the mono binary at build time. What could cause such a hidden
> version entry to _etext to end up in a binary like that?
It seems that this is caused by the verioning linker scripts that mono
uses.
First it links libmono.so with this:
VER_1 {
global:
mono_*;
GC_push_all_stack;
GC_start_blocking;
GC_end_blocking;
gc_thread_vtable;
local:
*;
};
Then it links everything together, including libmono.so, into the
"mono" binary using this versioning linker script:
{
global:
mono_*;
GC_push_all_stack;
GC_start_blocking;
GC_end_blocking;
gc_thread_vtable;
local:
*;
};
and that seems to be how we end up with that weird _etext versioning
entry above.
prev parent reply other threads:[~2006-03-29 1:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-29 0:23 David S. Miller
2006-03-29 1:46 ` David S. Miller [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=20060328.174701.11633966.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=libc-hacker@sources.redhat.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).