From: Keith Owens <kaos@ocs.com.au>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Ksymoops
Date: Wed, 01 Aug 2001 13:12:18 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005978@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005944@msgid-missing>
On Fri, 27 Jul 2001 10:08:11 -0400,
"peck, william" <peck_william@emc.com> wrote:
>Has anyone here used ksymoops on ia64? I don't know if I am doing anything
>wrong but I get an awful lot of warnings when I try to run a panic through
>it on ia64.
Thanks for the test reports (off list). It is obvious what is wrong,
/proc/ksyms does not list the address of functions, instead it lists
the address of the function pointer which contains { &function, GP }.
That breaks all the assumptions used by ksymoops and other debuggers
which rely on symbol tables. System.map lists the real function
addresses. By coincidence, all my ia64 ksymoops runs were done from
ix86 (cross debug mode) using just System.map, no ksyms.
I need to think about the best way of handling this. insmod needs the
function pointer, ksymoops needs the real function address. Ideally
ksyms should list both addresses, the pointer and the real function
address. That will be tricky given the current EXPORT_SYMBOL()
mechanism, there is no obvious way to distinguish between functions and
other addresses, this problem only applies to functions.
prev parent reply other threads:[~2001-08-01 13:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-27 14:08 [Linux-ia64] Ksymoops peck, william
2001-07-28 5:18 ` Keith Owens
2001-08-01 13:12 ` Keith Owens [this message]
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-105590693005978@msgid-missing \
--to=kaos@ocs.com.au \
--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