From: Keith Owens <kaos@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: 2.6.3 Heisenbug in unwind.c
Date: Tue, 24 Feb 2004 12:05:37 +0000 [thread overview]
Message-ID: <2654.1077624337@ocs3.ocs.com.au> (raw)
I am seeing a Heisenbug in the 2.6.3 kernel unwind code. The symptoms
are that the backtrace terminates early, usually failing to unwind past
an interrupt frame. Andreas, this _may_ be what you are seeing.
Changing the config options (sn2->dig) makes backtrace work again.
Turning on UNW_DEBUG to debug the unwinder makes backtrace work again :(.
Adding 30 dummy functions (which only call printk and are never called
themselves) to unwind.c makes the backtrace work again.
That last one really worries me. All it does is shift the position of
the real unwind code within the kernel without changing the unwind code
itself. Looks like an uninitialised pointer somewhere.
gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-24)
GNU assembler version 2.14.90.0.4 (ia64-unknown-linux-gnu) using BFD version 2.14.90.0.4 20030523
next reply other threads:[~2004-02-24 12:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-24 12:05 Keith Owens [this message]
2004-02-24 14:29 ` 2.6.3 Heisenbug in unwind.c David Mosberger
2004-03-10 5:27 ` Keith Owens
2004-03-11 7:56 ` David Mosberger
2004-03-11 8:14 ` Keith Owens
2004-03-15 6:52 ` Keith Owens
2004-03-16 6:22 ` Keith Owens
2004-03-16 10:42 ` Keith Owens
2004-03-17 22:46 ` Keith Owens
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=2654.1077624337@ocs3.ocs.com.au \
--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