From: Eli Zaretskii <eliz@is.elta.co.il>
To: davea@quasar.engr.sgi.com
Cc: ac131313@cygnus.com, jkingdon@engr.sgi.com, gdb@sources.redhat.com
Subject: Re: GDB on SGI Irix 6.5
Date: Thu, 17 May 2001 08:58:00 -0000 [thread overview]
Message-ID: <200105171559.SAA14958@is.elta.co.il> (raw)
In-Reply-To: <200104212007.NAA27159@quasar.engr.sgi.com>
> Date: Sat, 21 Apr 2001 13:07:12 -0700 (PDT)
> From: David B Anderson <davea@quasar.engr.sgi.com>
>
> n32 and 64 use dwarf2 debug information.
> For -64 IRIX cc/CC/etc dwarf2 has 64bit offsets and lengths
> (which goes beyond the literal dwarf2 standard --
> when using elf64 we decided to use 64bit offsets in dwarf in case
> a section got beyond what 32bits could address).
>
> Because of the dwarf2-by-IRIX difference from standard dwarf2
> a multi-arch for IRIX -64 using IRIX dwarf2-64 seems necessary,
> but that is a separate topic
Okay, I'm now staring at this topic, and it stares right back at me ;-)
Trying to debug a 64-bit executable produces the following error
message:
Dwarf Error: wrong version in compilation unit header.
This comes from the following fragment in
dwarf2read.c:dwarf2_build_psymtabs_hard:
while ((unsigned int) (info_ptr - dwarf_info_buffer)
+ ((info_ptr - dwarf_info_buffer) % 4) < dwarf_info_size)
{
struct comp_unit_head cu_header;
beg_of_comp_unit = info_ptr;
info_ptr = read_comp_unit_head (&cu_header, info_ptr, abfd);
if (cu_header.version != 2)
{
error ("Dwarf Error: wrong version in compilation unit header.");
return;
}
Debugging GDB with itself, I see that cu_header.version is zero,
probably because of the different format of the dwarf2 info used by
the 64-bit executables.
Where can I find the information about this format, and how it differs
from the standard dwarf2? "man dwarf" mumbles something about
/usr/share/src/compiler/dwarf/dwarf.v2.mm, but it doesn't exist on
this box, probably because they didn't install some optional package.
Is there any other place to find this document?
TIA
next prev parent reply other threads:[~2001-05-17 8:58 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 [this message]
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
[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
[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-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=200105171559.SAA14958@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=ac131313@cygnus.com \
--cc=davea@quasar.engr.sgi.com \
--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