From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Ingo Molnar" <mingo@elte.hu>,
"Arjan van de Ven" <arjan@linux.intel.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Error in save_stack_trace() on x86_64?
Date: Sun, 11 May 2008 15:09:28 +0200 [thread overview]
Message-ID: <19f34abd0805110609lf3180dm3b1078e373983ad7@mail.gmail.com> (raw)
Hi,
I am having a problem with v2.6.26-rc1 on x86_64. It seems that
save_stack_trace() is not able to follow page fault boundaries, since
all my saved traces look like this:
RIP: 0010:[<ffffffff8039b004>] [<ffffffff8039b004>] add_uevent_var+0xb4/0x160
...
[<ffffffff80221f97>] kmemcheck_read+0x127/0x1e0
[<ffffffff80222269>] kmemcheck_access+0x179/0x1d0
[<ffffffff8022231f>] kmemcheck_fault+0x5f/0x80
[<ffffffff8061cd1e>] do_page_fault+0x4de/0x8d0
[<ffffffff8061a7d9>] error_exit+0x0/0x51
[<ffffffffffffffff>] 0xffffffffffffffff
I have this in my .config:
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_STACKTRACE=y
...
CONFIG_FRAME_POINTER=y
...
CONFIG_DEBUG_INFO=y
On 32-bit, I am able to see the calls leading up to the page fault as
well. Did I miss something here?
Vegard
--
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
-- E. W. Dijkstra, EWD1036
next reply other threads:[~2008-05-11 13:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-11 13:09 Vegard Nossum [this message]
2008-05-11 19:44 ` Arjan van de Ven
2008-05-11 19:56 ` Vegard Nossum
2008-05-11 19:58 ` Arjan van de Ven
2008-05-18 17:13 ` Vegard Nossum
2008-05-18 18:31 ` Vegard Nossum
2008-05-18 18:52 ` Arjan van de Ven
2008-05-18 20:23 ` Vegard Nossum
2008-05-11 20:46 Vegard Nossum
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=19f34abd0805110609lf3180dm3b1078e373983ad7@mail.gmail.com \
--to=vegard.nossum@gmail.com \
--cc=arjan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
all inboxes | Powered by JetHome®