From: davea@quasar.engr.sgi.com (David B Anderson)
To: rsomerv@integrageo.com, somervil@cadvision.com, ac131313@cygnus.com
Cc: gdb@sourceware.cygnus.com
Subject: Re: does GDB support IRIX 64 bit executables?
Date: Thu, 01 Jun 2000 12:39:00 -0000 [thread overview]
Message-ID: <200006011943.MAA35397@quasar.engr.sgi.com> (raw)
> robert somerville wrote:
>Andrew Cagney wrote:
>>
>> robert somerville wrote:
>> >
>> > especially executables produced by the MIPSpro compilers
>>
>> Um, can you be a little bit more specific? Which ABI and native or
>> cross? GDB internaly supports a number of MIPS ABIs, some 32 bit, some
>> 64 bit and some which are suffering an identity crisis.
>>
>> enjoy,
>> Andrew
>
>
>the native MIPSpro 7.3 series of compilers (f77/cc) in 64 bit mode (
>-64 flag )
>on R10000/R12000 chips.
>
>I don't see a configuration option to build GDB for a 64bit enviroment,
>the default GDB build for IRIX6.5; 4.18/5.0 pukes, says
>wrong DWARF version on a 64bit executable. I suppose I could try gcc
>in 64 bit, but then f77 would be an issue for me.
The dwarf2 standard says that various things are 32 bit in dwarf2.
Such as section offsets.
SGI emits dwarf2 with 64bit offsets because it just seemed
short-sighted to have elf64 with 64 bit offsets and no
way to support really large dwarf sections.
gdb is following the dwarf standard, so dwarf2read.c does
not understand the SGI 64bit offsets-etc-in-dwarf2.
(no such 64bit offsets were defined in the dwarf standard)
I don't have a patch for this. At this time. Sorry.
I'd love to do one. I've made a note on my TODO list,
but have not checked the gdb TODO list on this...
[SGI has not seen any sections as big as 4GByte, but
I have heard of 1GB dwarf sections. The dwarf2 standard
committee has adopted a means of
allowing (not requiring) 64bit offsets in dwarf.
Support for compatibly reading the new stuff is not
supported yet either in dwarf2read.c
(no reason it should be in gdb at this time). ]
David B. Anderson davea@sgi.com danderson@acm.org http://reality.sgi.com/davea/
next reply other threads:[~2000-06-01 12:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-01 12:39 David B Anderson [this message]
2000-06-01 15:06 ` robert somerville
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=200006011943.MAA35397@quasar.engr.sgi.com \
--to=davea@quasar.engr.sgi.com \
--cc=ac131313@cygnus.com \
--cc=gdb@sourceware.cygnus.com \
--cc=rsomerv@integrageo.com \
--cc=somervil@cadvision.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