From: Daniel Berlin <dan@cgsoftware.com>
To: David B Anderson <davea@quasar.engr.sgi.com>
Cc: ezannoni@cygnus.com, Eli Zaretskii <eliz@is.elta.co.il>,
jimb@cygnus.com, gdb@sources.redhat.com, cagney@cygnus.com
Subject: Re: GDB on SGI Irix 6.5
Date: Wed, 13 Jun 2001 21:19:00 -0000 [thread overview]
Message-ID: <87d787itgl.fsf@cgsoftware.com> (raw)
In-Reply-To: <200106132033.NAA33197@quasar.engr.sgi.com>
David B Anderson <davea@quasar.engr.sgi.com> writes:
>|
>|> From: Elena Zannoni <ezannoni@cygnus.com>
>|> Date: Tue, 12 Jun 2001 16:03:49 -0400
>|>
>|> Andrew Cagney writes:
>|> > [I'll take the liberty of adding Elena and Jim. Might be useful to pose
>|> > any follow on questions on gdb@]
>|> >
>|> > > On Thu, 17 May 2001, David B Anderson wrote:
>|> > >
>|> > >
>|> > >> 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.
>|> > >
>|> > >
>|>
>|> Are these the only differences? Is anything SGI specific encoded in the
>|> 'version' field of cu_header? Maybe that can be used. Is there somewhere
>|> in the debug info a field that tells that this is SGI's version?
>|
>|I don't see anything in the documents I got from Dave's site. Dave,
>|could you please answer these questions?
>|
>|Thanks for the other advice, I will look that up.
>
> Hopefully already anwered. No, other field in dwarf2.
>
> However, because IRIX is big-endian, and because no
> compilation unit should have an
> initial-length
> field with all zero bits,
>
> A test for a dwarf2 CU (compilation unit)
> initial-length of zero followed 4 bytes
> later by a correct version number for dwarf2
> might suffice (in an elf64 big endian object) folowed by setting
> up the initial_length_size and offset_size
> as above might suffice.
This is correct. The initial length should never be zero. Even for
64 bit dwarf 2.1, it's 0xffffffff followed by 8 bytes of the real
initial length.
>
> Whether this can be done sensibly multi-arch in gdb is not clear to me.
>
> davea@sgi.com
--
"How young can you die of old age?
"-Steven Wright
next prev parent reply other threads:[~2001-06-13 21:19 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
[not found] <npae3c16ia.fsf@zwingli.cygnus.com>
2001-06-14 0:52 ` Eli Zaretskii
2001-06-14 10:05 ` Daniel Berlin
[not found] <200106131650.JAA27856@quasar.engr.sgi.com>
2001-06-13 11:40 ` Eli Zaretskii
2001-06-13 13:05 ` Andrew Cagney
2001-06-13 1:53 Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2001-05-17 10:15 David B Anderson
2001-05-17 11:40 ` 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=87d787itgl.fsf@cgsoftware.com \
--to=dan@cgsoftware.com \
--cc=cagney@cygnus.com \
--cc=davea@quasar.engr.sgi.com \
--cc=eliz@is.elta.co.il \
--cc=ezannoni@cygnus.com \
--cc=gdb@sources.redhat.com \
--cc=jimb@cygnus.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