From: Daniel Berlin <dan@www.cgsoftware.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: <davea@quasar.engr.sgi.com>, <ac131313@cygnus.com>,
<jkingdon@engr.sgi.com>, <gdb@sources.redhat.com>
Subject: Re: GDB on SGI Irix 6.5
Date: Thu, 17 May 2001 09:41:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.33.0105171233470.12958-100000@www.cgsoftware.com> (raw)
In-Reply-To: <Pine.SUN.3.91.1010517192835.14953B-100000@is>
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.
>
next prev parent reply other threads:[~2001-05-17 9:41 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2001-05-17 11:33 ` Eli Zaretskii
2001-05-17 11:47 ` Daniel Berlin
[not found] <npae3c16ia.fsf@zwingli.cygnus.com>
2001-06-14 0:52 ` Eli Zaretskii
2001-06-14 10:05 ` Daniel Berlin
[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
[not found] <200106131650.JAA27856@quasar.engr.sgi.com>
2001-06-13 11:40 ` Eli Zaretskii
2001-06-13 13:05 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2001-06-13 1:53 Eli Zaretskii
2001-05-17 10:15 David B Anderson
2001-05-17 11:40 ` Eli Zaretskii
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=Pine.LNX.4.33.0105171233470.12958-100000@www.cgsoftware.com \
--to=dan@www.cgsoftware.com \
--cc=ac131313@cygnus.com \
--cc=davea@quasar.engr.sgi.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