From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: davea@quasar.engr.sgi.com
Cc: ac131313@cygnus.com, gdb@sources.redhat.com
Subject: Re: GDB on SGI Irix 6.5
Date: Wed, 13 Jun 2001 11:40:00 -0000 [thread overview]
Message-ID: <3405-Wed13Jun2001213809+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <200106131650.JAA27856@quasar.engr.sgi.com>
> Date: Wed, 13 Jun 2001 09:50:09 -0700 (PDT)
> From: David B Anderson <davea@quasar.engr.sgi.com>
>
> The irix 64 dwarf2 debug info is identical
> to what dwarf2read.c reads (and only dwarf2read, not anything else)
> except for the initial bytes of CU being 8 bytes, not 12
> (see dwarf2read) and the determination of offset and length
> size being based on 'IRIX6.5' not on internal evidence in the dwarf
> itself.
So you are saying that there's nothing in the file--not a single
thing--that would allow GDB to find out if the debug info is for 64 or
n32 ABI?
Would it be reasonable then to try one format, and if that fails, try
the other? (I know that it fails somewhere, because when I try to
debug a 64-bit executable with GDB built from current CVS, it
complains about something like ``wrong version'' (IIRC).)
next parent reply other threads:[~2001-06-13 11:40 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200106131650.JAA27856@quasar.engr.sgi.com>
2001-06-13 11:40 ` Eli Zaretskii [this message]
2001-06-13 13:05 ` Andrew Cagney
[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] <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
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=3405-Wed13Jun2001213809+0300-eliz@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 \
/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).