linux-mips
[Top] [All Lists]

ksymoops on origin

To: Ralf Baechle <ralf@oss.sgi.com>
Subject: ksymoops on origin
From: Keith Owens <kaos@ocs.com.au>
Date: Fri, 05 Jan 2001 11:42:42 +1100
Cc: "'linux-mips@oss.sgi.com'" <linux-mips@oss.sgi.com>
In-reply-to: Your message of "Thu, 04 Jan 2001 15:13:34 -0200." <20010104151334.C2525@bacchus.dhis.org>
Sender: owner-linux-mips@oss.sgi.com
On Thu, 4 Jan 2001 15:13:34 -0200, 
Ralf Baechle <ralf@oss.sgi.com> wrote:
>Doesn't really solve the problem.  For example on an Origin we have a 32-bit
>userland but 64-bit kernel addresses which confuses ksymops and procps.

In what way does ksymoops get confused?  All its address handling
should be 64 bit.  As long as the kernel prints its addresses in full,
without removing the high order word, then the text handling should be
OK.  The only problem will be the default object format which is taken
from ksymoops itself.  Sparc also has this problem, from oops.c,
function Oops_eip.

        /* Special case for sparc64.  If the output target is defaulting to the
         * same format as ksymoops then the default is wrong, kernel is 64 bit,
         * ksymoops is 32 bit.  When we see an EIP from sparc64, set the correct
         * default.
         */
        if (!options->target && !options->architecture &&
            strcmp(bfd_get_target(ibfd), "elf32-sparc")) {
            options->target = "elf64-sparc";
            options->architecture = "sparc:v9a";
        }

I will add a special case for Origin if somebody can tell me:

  What oops string identifies a 64 bit kernel instead of 32 bit.
  What bfd_get_target() reports for a 32 bit ksymoops on Origin.
  What target and architecture to use for a 64 bit kernel.

Even without special case code for Origin, you can run ksymoops with
the -t and -a options to force the desired format, instead of
defaulting to the format of ksymoops.


<Prev in Thread] Current Thread [Next in Thread>