Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: Keith Owens <kaos@melbourne.sgi.com>
Cc: Florian Lohoff <flo@rfc822.org>,
	Raoul Borenius <borenius@shuttle.de>,
	linux-mips@oss.sgi.com
Subject: Re: Kernel crash on boot with current cvs (todays)
Date: Wed, 13 Jun 2001 14:05:51 +0200	[thread overview]
Message-ID: <20010613140550.B31221@bacchus.dhis.org> (raw)
In-Reply-To: <7964.992432058@ocs4.ocs-net>; from kaos@melbourne.sgi.com on Wed, Jun 13, 2001 at 09:34:18PM +1000

On Wed, Jun 13, 2001 at 09:34:18PM +1000, Keith Owens wrote:

> On Wed, 13 Jun 2001 12:56:10 +0200, 
> Florian Lohoff <flo@rfc822.org> wrote:
> >> Using ksymoops gave a lot of warnings this time. Don't know why, the
> >> System.map should be the right one (it's out of
> >> kernel-image-2.4.3-ip22-r4k.tgz).
> >
> >This is because the system map has been generated with newer binutils
> >which always dump the addresses as 64Bit addresses.
> 
> Looks like I need to add a new option to ksymoops.  -T <bits>, truncate
> all addresses to this bit size.  Added to my list for the next ksymoops
> release.

That can be done automatically.  For 32-bit ELF files mips*-linux binutils
dump some of the addresses as 32-bit addresses, some as sign-extended (!)
64-bit addresses.  So ksymops should just sign extend any 32-bit addresses
to 64-bit and then work on full lenght addresses.

Is ksymoops able to handle 64-bit addresses when running on a 32-bit host?
That is a common case for many people when decoding their MIPS oopses.

  Ralf

  reply	other threads:[~2001-06-13 12:06 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-10 22:03 Kernel crash on boot with current cvs (todays) Florian Lohoff
2001-06-11  3:53 ` Keith Owens
2001-06-11 19:12   ` Florian Lohoff
2001-06-12  1:01     ` Maciej W. Rozycki
2001-06-12  1:01       ` Keith M Wesolowski
2001-06-12  1:22         ` Maciej W. Rozycki
2001-06-12  2:05       ` Keith Owens
2001-06-11  4:42 ` Ralf Baechle
2001-06-11 14:50   ` Raoul Borenius
2001-06-12 10:09     ` Florian Lohoff
2001-06-12 11:53       ` Ralf Baechle
2001-06-12 16:37         ` H . J . Lu
     [not found]         ` <20010613100602.A17124@bunny.shuttle.de>
2001-06-13 10:56           ` Florian Lohoff
2001-06-13 11:34             ` Keith Owens
2001-06-13 12:05               ` Ralf Baechle [this message]
2001-06-13 12:19                 ` ksymoops changes for mips (was Kernel crash on boot with current cvs) Keith Owens
2001-06-16  9:22                   ` Ralf Baechle
2001-06-27  2:21                   ` ksymoops changes for mips Keith Owens
2001-06-28 14:32                     ` Thiemo Seufer
2001-07-31  3:57                       ` Keith Owens
2001-07-31  4:30                         ` Keith Owens
2001-08-03  6:10                       ` Keith Owens
2001-08-03 10:07                         ` Thiemo Seufer
2001-06-13 13:44                 ` Kernel crash on boot with current cvs (todays) Maciej W. Rozycki
2001-06-13 14:07                   ` Keith Owens
2001-06-13 15:08                     ` Maciej W. Rozycki
2001-06-16  9:24                   ` Ralf Baechle
2001-06-13 11:37             ` Raoul Borenius
2001-06-13 11:46               ` Keith Owens
2001-06-13 11:46                 ` Keith Owens
2001-06-13 13:16                 ` Raoul Borenius

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=20010613140550.B31221@bacchus.dhis.org \
    --to=ralf@oss.sgi.com \
    --cc=borenius@shuttle.de \
    --cc=flo@rfc822.org \
    --cc=kaos@melbourne.sgi.com \
    --cc=linux-mips@oss.sgi.com \
    /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