From: Richard Henderson <rth@redhat.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: problem with unwind info for .init/.fini sections
Date: Sat, 23 Feb 2002 00:58:08 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905180@msgid-missing> (raw)
On Fri, Feb 22, 2002 at 11:54:27AM -0800, David Mosberger wrote:
> While we found the problem with ia64 linux, I suspect other
> platforms that rely on unwind info are likely to be affected as well.
This is .init -- why do you care if you can unwind through it?
r~
next reply other threads:[~2002-02-23 0:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-23 0:58 Richard Henderson [this message]
2002-02-23 1:01 ` [Linux-ia64] Re: problem with unwind info for .init/.fini sections David Mosberger
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-105590701905180@msgid-missing \
--to=rth@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.