From: Jim Wilson <wilson@cygnus.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Buggy unwind tables in user space
Date: Mon, 21 May 2001 23:12:39 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005637@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005627@msgid-missing>
>Most IA64 distributions contain a bad version of crtn.o. Executables
>or shared libraries built with this file have invalid unwind data.
I'm assuming this is a glibc problem, and that there is nothing I need to do.
Glibc by default creates crti/crtn by compiling one C file, and then spliting
the output into two assembly language files. This works on systems with
dumb assemblers. It does not work on IA-64. This was changed in August 2000.
crti/crtn are now generated from IA-64 assembly.
>Correction. Redhat 7.0.98 (Wolverine) also has a buggy version of
>crtn.o.
You will have to elaborate. My copy here has no unwind info, and hence the
unwind info can't possibly be missing relocations.
If your complaint is that there is no unwind info, then it needs to be
added to the assembly code in glibc. See libc/sysdeps/ia64/elf/initfini.c.
Jim
prev parent reply other threads:[~2001-05-21 23:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-19 3:45 [Linux-ia64] Buggy unwind tables in user space Keith Owens
2001-05-19 16:04 ` Andreas Schwab
2001-05-21 2:03 ` Keith Owens
2001-05-21 23:12 ` Jim Wilson [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=marc-linux-ia64-105590693005637@msgid-missing \
--to=wilson@cygnus.com \
--cc=linux-ia64@vger.kernel.org \
/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