linux-mips
[Top] [All Lists]

Re: ksymoops and 64 bit mips

To: Ralf Baechle <ralf@linux-mips.org>
Subject: Re: ksymoops and 64 bit mips
From: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Date: Thu, 9 Jan 2003 15:03:14 +0100 (MET)
Cc: Gilad Benjamini <gilad@riverhead.com>, linux-mips@linux-mips.org
In-reply-to: <20030109143822.A23928@linux-mips.org>
Organization: Technical University of Gdansk
Original-recipient: rfc822;linux-mips@linux-mips.org
Sender: linux-mips-bounce@linux-mips.org
On Thu, 9 Jan 2003, Ralf Baechle wrote:

> > Initially I got a lot of garbage.
> > Upgrdaing to ksymoops 2.4.5 , and using the --truncate=1 and 
> > -t elf32-little reduced 
> > the amount of garbage, but still all the output shown
> > was "No symbol available".
> > 
> > Any additional things I should do ?
> 
> Possibly your ksymoops is get confused by the System.map file.  The vmlinux
> file is a 32-bit ELF file but the System.map file contains the addresses
> sign-extended to 64-bit.  As a bandaid you can just chop off the high
> 32-bits of all addresses in System.map.

 Recent versions of ksymoops contain code to handle 64-bit MIPS flexibly
and are expected to take care of address aliases.  They don't works very
well, though, and I've done a few fixes.  They are available in a ksymoops
2.4.8 package at my site and hopefully will be applied in a future
release.

 Anyway the cross-ksymoops case referred by Gilad is tricky -- you need to
build ksymoops linking against an appropriate BFD library, i.e. one that
supports a MIPS64 target.  Additionally MIPS64-specific nm and objdump
programs have to be available to that ksymoops binary (cf. KSYMOOPS_NM and
KSYMOOPS_OBJDUMP environment variables). 

 For detailed information on using a cross-setup see the ksymoops
documentation.

-- 
+  Maciej W. Rozycki, Technical University of Gdansk, Poland   +
+--------------------------------------------------------------+
+        e-mail: macro@ds2.pg.gda.pl, PGP key available        +


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