public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: David B Anderson <davea@quasar.engr.sgi.com>
To: Eli Zaretskii <eliz@is.elta.co.il>,
	Daniel Berlin <dan@www.cgsoftware.com>
Cc: <gdb@sources.redhat.com>, <jkingdon@engr.sgi.com>,
	<ac131313@cygnus.com>, <davea@quasar.engr.sgi.com>
Subject: Re: GDB on SGI Irix 6.5
Date: Thu, 17 May 2001 10:15:00 -0000	[thread overview]
Message-ID: <200105171713.KAA28412@quasar.engr.sgi.com> (raw)

Daniel Berlin wrote:
|On Thu, 17 May 2001, Eli Zaretskii wrote:
|
|>
|> On Thu, 17 May 2001, Daniel Berlin wrote:
|>
|> > We should support 64 bit dwarf2 already, for the most part.
|>
|> Since when?
|Well, since about august of last year or something.
|
|The main difference between 64 bit dwarf2, and 32 bit dwarf2, is, of
|course, the offset sizes.
|
|The DWARF2.1 standard says that the cu header's initial length will tell
|us whether we are dealing with 4 byte offsets or 8 byte offsets.
|
|If you look at dwarf2read.c, you'll notice it handles offset sizes of both
|4 and 8.
|read_initial_length takes care of figuring out which offset size we have.
|
|
|> It's possible that I have an outdated tree, in which case I'm sorry for
|> the line noise.


The 64bit dwarf2 that is read by read_initial_length is based on
dwarf 2.1, designed in 2000.  SGI 64bit dwarf2 was designed in
the early 1990's.  SGI made offsets etc 64bit in elf64
(and offsets etc 32bits in elf32).    
(basically we could not bring ourselves to limit dwarf 
offsets to 32 bits in an elf64 file...)

Anyway,  to be correct for IRIX6,  read_initial_length
needs to know it is IRIX elf64 and then
	 /* UNTESTED, NOT ALL THAT NEEDS TO BE DONE probably */
         cu_header->initial_length_size = 8;
         cu_header->offset_size = 8;
at least gives the right sizes.

Ben Gamsa's patch on my website is a crude version of the above
(not suitable for inclusion in gdb, but at least it has the
key changes IRIX6 elf64 dwarf2 requires, for an older gdb).
(patch is not multi-arch.)
See the end of the page
	http://reality.sgi.com/davea/objectinfo.html
(which Eli already noticed).

I'm on vacation all week, but I'll apply Eli's patches
and try out gdb asap.  Hopefully tonight or tomorrow night.
Been kind of behind in email due to vacation.

Regards,
David B. Anderson davea@sgi.com danderson@acm.org http://reality.sgi.com/davea/

             reply	other threads:[~2001-05-17 10:15 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-17 10:15 David B Anderson [this message]
2001-05-17 11:40 ` Eli Zaretskii
     [not found] <npae3c16ia.fsf@zwingli.cygnus.com>
2001-06-14  0:52 ` Eli Zaretskii
2001-06-14 10:05   ` Daniel Berlin
2001-06-14 15:54   ` Jim Blandy
     [not found] <200106131650.JAA27856@quasar.engr.sgi.com>
2001-06-13 11:40 ` Eli Zaretskii
2001-06-13 13:05   ` Andrew Cagney
     [not found] <Pine.SUN.3.91.1010612152328.3699B-100000@is>
     [not found] ` <3B266F35.50007@cygnus.com>
     [not found]   ` <15142.30117.72465.686304@kwikemart.cygnus.com>
2001-06-13  1:55     ` Eli Zaretskii
2001-06-13 13:35     ` David B Anderson
2001-06-13 21:19       ` Daniel Berlin
  -- strict thread matches above, loose matches on Subject: below --
2001-06-13  1:53 Eli Zaretskii
2001-04-19 18:06 David B Anderson
2001-04-21 11:12 ` Eli Zaretskii
2001-04-21 12:09   ` Paul Hilfinger
2001-04-21 13:09 ` David B Anderson
2001-04-21 13:19   ` Eli Zaretskii
2001-05-17  8:58   ` Eli Zaretskii
2001-05-17  9:15     ` Eli Zaretskii
2001-05-17  9:26       ` Daniel Berlin
2001-05-17  9:28         ` Eli Zaretskii
2001-05-17  9:41           ` Daniel Berlin
2001-05-17 11:33             ` Eli Zaretskii
2001-05-17 11:47               ` Daniel Berlin
2001-04-09  0:08 Eli Zaretskii
2001-04-09  6:53 ` Daniel Berlin
2001-04-17 10:38 ` Andrew Cagney
2001-04-18  9:29   ` Eli Zaretskii
2001-04-19  6:08     ` Eli Zaretskii
2001-04-30 10:01       ` Andrew Cagney
2001-04-30 11:28         ` Eli Zaretskii

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=200105171713.KAA28412@quasar.engr.sgi.com \
    --to=davea@quasar.engr.sgi.com \
    --cc=ac131313@cygnus.com \
    --cc=dan@www.cgsoftware.com \
    --cc=eliz@is.elta.co.il \
    --cc=gdb@sources.redhat.com \
    --cc=jkingdon@engr.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).