From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Unwind can load wrong data from pt_regs
Date: Mon, 09 Dec 2002 21:21:07 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709805525@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805516@msgid-missing>
>>>>> On Mon, 09 Dec 2002 19:35:03 +1100, Keith Owens <kaos@sgi.com> said:
Keith> This implicitly assumes that when a fr or br register is
Keith> required from pt_regs, info->sp is pointing to pt_regs. But
Keith> info->sp is modified as the code unwinds through each
Keith> function. The above code only gives correct results for
Keith> register lookups from the failing function. Unwinding and
Keith> accessing a fr or br register from earlier functions loads
Keith> incorrect values for those registers.
Yes, this is something that has been fixed already in the user-level
libunwind. It's not hard to fix, just someone needs to get around to
do it. I don't think it's a critical issue, since it only happens for
nested traps. I assume you saw this with kdb?
--david
next prev parent reply other threads:[~2002-12-09 21:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-09 8:35 [Linux-ia64] Unwind can load wrong data from pt_regs Keith Owens
2002-12-09 21:21 ` David Mosberger [this message]
2002-12-09 22:04 ` Keith Owens
2002-12-09 22:17 ` 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-105590709805525@msgid-missing \
--to=davidm@napali.hpl.hp.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.