public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Buggy unwind tables in user space
Date: Mon, 21 May 2001 02:03:50 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590693005629@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005627@msgid-missing>

On Sat, 19 May 2001 13:45:27 +1000, 
Keith Owens <kaos@ocs.com.au> wrote:
>Most IA64 distributions contain a bad version of crtn.o.  Executables
>or shared libraries built with this file have invalid unwind data.
>
>SuSe Linux 7.1a, TurboLinux 000828, TL 010307 (beta3) and Redhat 7.0.90
>all have a buggy version of crtn.o.  Redhat 7.0.98 (Wolverine) has a
>clean version of crtn.o, but if any Wolverine binaries were compiled
>against the old crtn.o then they will be bad as well.

Correction.  Redhat 7.0.98 (Wolverine) also has a buggy version of
crtn.o.



  parent reply	other threads:[~2001-05-21  2:03 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 [this message]
2001-05-21 23:12 ` Jim Wilson

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-105590693005629@msgid-missing \
    --to=kaos@ocs.com.au \
    --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