From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: cagney@gnu.org, jkj@sco.com
Cc: ezannoni@redhat.com, gdb@sources.redhat.com, jimb@redhat.com,
mec.gnu@mindspring.com
Subject: Re: Phasing out Dwarf 1?
Date: Wed, 05 May 2004 22:01:00 -0000 [thread overview]
Message-ID: <20040505220132.260584B104@berman.michael-chastain.com> (raw)
Kean Johnston writes:
> At least 3 I know of: SCO, UnixWare ans Solaris x86. DG-UX may as well,
> but I cant swear to its native debugging format.
OpenServer and UnixWare:
AFAIK, it's still FSF's policy to support SCO's platforms. I disagree
with this policy but if dwarf-1 is needed for OpenServer and UnixWare
then gdb has to keep supporting dwarf-1.
Solaris X86:
Mark, can you say anything about this? What debug format does "cc -g"
produce on a solaris x86 machine?
DG-UX:
I looked into this in February 2003. Takis Psarogiannakopoulus
developed a native toolchain for this platform based on dwarf-2.
Takis said that his port is based on dwarf-2. More importantly,
Takis said that the FSF version of gdb has *never* worked on dg-ux
(his emphasis) and might as well just be removed.
http://sources.redhat.com/ml/gdb/2003-02/msg00074.html
The FSF sent Takis a copyright assignment. I don't know if he
executed it or not, but he balked at getting a disclaimer from
his employer. And nobody has done any work to merge Takis's
work back into FSF gdb.
Since last year, EMC (the owner of Data General) has put all
their web pages for dg-ux support behind a login barrier and
requires a support contract to read them. So I can't say what
has happened with dg-ux lately. As of 2003-02, the most recent
version of dg-ux was DG/UX 4.20MU07, released 2001-04.
Michael C
next reply other threads:[~2004-05-05 22:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-05 22:01 Michael Elizabeth Chastain [this message]
2004-05-06 14:02 ` Andrew Cagney
2004-05-06 20:11 ` Mark Kettenis
-- strict thread matches above, loose matches on Subject: below --
2004-05-06 15:00 Michael Elizabeth Chastain
2004-05-07 1:19 ` Andrew Cagney
2004-05-05 21:33 Michael Elizabeth Chastain
2004-05-05 5:24 Michael Elizabeth Chastain
2004-05-05 14:31 ` Andrew Cagney
2004-05-05 16:05 ` Kean Johnston
2004-05-05 18:30 ` Stan Shebs
2004-05-05 18:53 ` Kean Johnston
2004-05-05 5:03 Michael Elizabeth Chastain
2004-05-03 15:56 Michael Elizabeth Chastain
2004-05-04 15:37 ` Andrew Cagney
2004-05-04 17:09 ` Nathan J. Williams
2004-05-04 17:19 ` Kean Johnston
2004-05-05 0:28 ` Stan Shebs
2004-05-05 5:57 ` Jim Blandy
2004-05-10 21:09 ` Andrew Cagney
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=20040505220132.260584B104@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=cagney@gnu.org \
--cc=ezannoni@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=jimb@redhat.com \
--cc=jkj@sco.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