From: Daniel Jacobowitz <drow@mvista.com>
To: Paul Mundt <pmundt@mvista.com>
Cc: gdb@sourceware.cygnus.com
Subject: Re: mips64 elf64 problems
Date: Sun, 25 Nov 2001 12:41:00 -0000 [thread overview]
Message-ID: <20011130154459.A27914@nevyn.them.org> (raw)
In-Reply-To: <20011130113108.A7288@mvista.com>
On Fri, Nov 30, 2001 at 11:31:08AM -0800, Paul Mundt wrote:
> I was in the process of testing out kgdb with a mips64 target (using gdb 5.1),
> and ran into a rather peculiar problem. I have two images.. the vmlinux.64 is
> the one that is being booted on the target:
>
> vmlinux: ELF 32-bit MSB executable, mips-4 MIPS R3000_BE, version 1,
> statically linked, not stripped
> vmlinux.64: ELF 64-bit MSB executable, mips-4 MIPS R3000_BE, version 1,
> statically linked, not stripped
>
> Upon trying to load these with gdb, the elf32 works just fine.. whereas the
> elf64 complains about not being able to read ECOFF debugging information:
>
> lethal@freya:~$ mips64-linux-gdb vmlinux
> GNU gdb 5.1
> Copyright 2001 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB. Type "show warranty" for details.
> This GDB was configured as "--host=i686-pc-linux-gnu --target=mips64-linux"...
> (gdb)
>
> lethal@freya:~$ mips64-linux-gdb vmlinux.64
> GNU gdb 5.1
> Copyright 2001 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB. Type "show warranty" for details.
> This GDB was configured as "--host=i686-pc-linux-gnu
> --target=mips64-linux"...Error reading ECOFF debugging information: File
> truncated
>
> (gdb)
>
> The kernels were both compiled with CONFIG_REMOTE_DEBUG turned on, so they
> were both compiled with -g.
>
> I've tried this with a --target of mips64-linux as well as mips64-linux-elf,
> and the same thing happens both times.
>
> Anyone have any insight on this?
What binutils version are you using to assemble (i.e. do you have
ECOFF/mdebug information at all)?
You're probably trying to use stabs (or mdebug) on a 64-bit binary. I
know stabs will whine; I don't know if I've ever tried mdebug. You
might want to use -gdwarf-2 instead, except of course Dwarf-2 is broken
on MIPS this month.
You might want to breakpoint in _bfd_mips_elf_read_ecoff_info in
elf64-mips.c. I see that there's only a 32-bit version of this, so if
any data structures change on 64-bit you'll lose.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2001-11-30 20:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-25 12:29 Paul Mundt
2001-11-25 12:41 ` Daniel Jacobowitz [this message]
2001-11-30 11:30 ` Paul Mundt
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=20011130154459.A27914@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sourceware.cygnus.com \
--cc=pmundt@mvista.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