From: Paulo Marques <pmarques@grupopie.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: /proc/kallsyms broken in 2.6.26-rc1-git6
Date: Fri, 09 May 2008 19:03:02 +0100 [thread overview]
Message-ID: <482491D6.9030205@grupopie.com> (raw)
In-Reply-To: <20080509174148.GA22246@basil.nowhere.org>
Andi Kleen wrote:
> Haven't investigated why yet, but this doesn't seem right:
>
> # cat /proc/kallsyms
> 0000000000000b0c N DW.aio.h.903a6d92.0
> 0000000000000b19 N DW.aio.h.903a6d92.1
> 0000000000000b24 N DW.aio.h.903a6d92.2
> 0000000000000bce N DW.task_io_accounting.h.8d8de327.0
> 0000000000000bec N DW.hrtimer.h.c23659c6.0
> 0000000000000bf5 N DW.hrtimer.h.c23659c6.1
> 0000000000000c00 N DW.hrtimer.h.c23659c6.2
> 0000000000000c06 N DW.hrtimer.h.c23659c6.3
> 0000000000000c28 N DW.hrtimer.h.c23659c6.4
> 0000000000000c2e N DW.hrtimer.h.c23659c6.5
> ...
> ffffffff80337043 u idr_pre_get [i2c_core]
> ffffc2000007573e ? DW.sched.h.920090ff.56 [i2c_core]
Are you compiling with CONFIG_KALLSYMS_ALL?
If you are, kallsyms will store all the output of "nm -n vmlinux" no
matter what section the symbol belongs to...
--
Paulo Marques - www.grupopie.com
"C++ : increment the value of C and use the old one"
next prev parent reply other threads:[~2008-05-09 19:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-09 17:41 /proc/kallsyms broken in 2.6.26-rc1-git6 Andi Kleen
2008-05-09 18:03 ` Paulo Marques [this message]
2008-05-09 19:36 ` Andi Kleen
2008-05-09 19:59 ` Paulo Marques
2008-05-09 23:16 ` Andi Kleen
2008-05-12 9:55 ` Paulo Marques
2008-05-12 10:08 ` Andi Kleen
2008-05-09 23:37 ` Alexey Dobriyan
2008-05-12 10:00 ` Paulo Marques
2008-05-12 15:50 ` Cyrill Gorcunov
2008-05-12 17:23 ` Sam Ravnborg
2008-05-12 17:28 ` Cyrill Gorcunov
2008-05-13 9:54 ` Andi Kleen
2008-05-19 18:11 ` Sam Ravnborg
2008-05-19 18:15 ` Cyrill Gorcunov
2008-05-19 18:21 ` Sam Ravnborg
2008-05-19 18:22 ` Cyrill Gorcunov
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=482491D6.9030205@grupopie.com \
--to=pmarques@grupopie.com \
--cc=andi@firstfloor.org \
--cc=linux-kernel@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.