Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Gilad Benjamini <gilad@riverhead.com>
To: 'Ralf Baechle' <ralf@linux-mips.org>,
	Gilad Benjamini <gilad@riverhead.com>
Cc: linux-mips@linux-mips.org
Subject: RE: ksymoops and 64 bit mips
Date: Thu, 09 Jan 2003 16:01:01 +0200	[thread overview]
Message-ID: <001801c2b7e7$8b3c04d0$7100000a@riverhead.com> (raw)
In-Reply-To: <20030109143822.A23928@linux-mips.org>

Au contraire.
System.map has 32 bit addresses, which I tried to sign extended 
with "ffffffff" (the wonders of sed), but that didn't help.

> -----Original Message-----
> From: Ralf Baechle [mailto:ralf@linux-mips.org]
> Sent: Thursday, January 09, 2003 3:38 PM
> To: Gilad Benjamini
> Cc: linux-mips@linux-mips.org
> Subject: Re: ksymoops and 64 bit mips
> 
> 
> On Wed, Jan 08, 2003 at 10:15:19PM +0200, Gilad Benjamini 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.
> 
>   Ralf
> 

  reply	other threads:[~2003-01-09 14:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-08 20:15 ksymoops and 64 bit mips Gilad Benjamini
2003-01-09 13:38 ` Ralf Baechle
2003-01-09 14:01   ` Gilad Benjamini [this message]
2003-01-09 14:03   ` Maciej W. Rozycki
  -- strict thread matches above, loose matches on Subject: below --
2003-01-09 14:01 Gilad Benjamini

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='001801c2b7e7$8b3c04d0$7100000a@riverhead.com' \
    --to=gilad@riverhead.com \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.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