From: Keith Owens <kaos@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] [patch] 2.4.21-pre5-bk arch/ia64/kernel/unwind.c
Date: Wed, 19 Mar 2003 03:08:55 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590723705268@msgid-missing> (raw)
David has said that he has applied the take the "read unwind data from
r0" patch to 2.5, so add it to 2.4. The check for info->pt before
calling get_scratch_regs() is a merge error, get_scratch_regs() does
all the checking (needs to be in 2.5 as well).
--- 2.4.21-pre5-ia64-bk/arch/ia64/kernel/unwind.c Wed Mar 19 11:56:52 2003
+++ linux/arch/ia64/kernel/unwind.c Wed Mar 19 14:03:57 2003
@@ -253,6 +253,11 @@
struct pt_regs *pt;
if ((unsigned) regnum - 1 >= 127) {
+ if (regnum = 0 && !write) {
+ *val = 0; /* read r0 always returns 0 */
+ *nat = 0;
+ return 0;
+ }
UNW_DPRINT(0, "unwind.%s: trying to access non-existent r%u\n",
__FUNCTION__, regnum);
return -1;
@@ -318,11 +323,6 @@
}
} else {
/* access a scratch register */
- if (!info->pt) {
- UNW_DPRINT(0, "unwind.%s: no pt-regs; cannot access r%d\n",
- __FUNCTION__, regnum);
- return -1;
- }
pt = get_scratch_regs(info);
addr = (unsigned long *) (pt + pt_regs_off(regnum));
if (info->pri_unat_loc)
reply other threads:[~2003-03-19 3:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-105590723705268@msgid-missing \
--to=kaos@sgi.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