From: Daniel Berlin <dan@cgsoftware.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: Jim Blandy <jimb@zwingli.cygnus.com>,
David B Anderson <davea@quasar.engr.sgi.com>,
Elena Zannoni <ezannoni@cygnus.com>,
gdb@sources.redhat.com
Subject: Re: GDB on SGI Irix 6.5
Date: Thu, 14 Jun 2001 10:05:00 -0000 [thread overview]
Message-ID: <87u21jgffh.fsf@cgsoftware.com> (raw)
In-Reply-To: <Pine.SUN.3.91.1010614105244.972F-100000@is>
Eli Zaretskii <eliz@is.elta.co.il> writes:
> On 13 Jun 2001, Jim Blandy wrote:
>
>> assuming we've decided a .debug_info section is carrying SGI 64-bit
>> Dwarf2 data, has someone already adapted dwarf2read to read the
>> data?
>
> There's a patch on Dave's site which is supposed to do that. That
> patch is against GDB 4.17, and is based on compile-time #ifdef's, but
> otherwise it should be fine.
>
> What I was trying to figure out was how to add this support in a
> cleaner way, so that Irix 6.x users will not need two different GDB
> binaries to debug programs, one each for each ABI.
You can check if the initial length is 0, followed by a valid number
(IE not zero).
If so, either we've got completely invalid dwarf2, or SGI's 64bit
dwarf2.
--
"It doesn't matter what temperature the room is, it's always room
temperature.
"-Steven Wright
next prev parent reply other threads:[~2001-06-14 10:05 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <npae3c16ia.fsf@zwingli.cygnus.com>
2001-06-14 0:52 ` Eli Zaretskii
2001-06-14 10:05 ` Daniel Berlin [this message]
[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
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=87u21jgffh.fsf@cgsoftware.com \
--to=dan@cgsoftware.com \
--cc=davea@quasar.engr.sgi.com \
--cc=eliz@is.elta.co.il \
--cc=ezannoni@cygnus.com \
--cc=gdb@sources.redhat.com \
--cc=jimb@zwingli.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