From: Stan Shebs <shebs@apple.com>
To: Kean Johnston <jkj@sco.com>
Cc: Andrew Cagney <cagney@gnu.org>,
Michael Elizabeth Chastain <mec.gnu@mindspring.com>,
ezannoni@redhat.com, gdb@sources.redhat.com, jimb@redhat.com
Subject: Re: Phasing out Dwarf 1?
Date: Wed, 05 May 2004 18:30:00 -0000 [thread overview]
Message-ID: <409932A9.3040504@apple.com> (raw)
In-Reply-To: <40990E80.4090906@sco.com>
Kean Johnston wrote:
>> If you installed operating system X, including the vendor compiler,
>> and typed `cc -g ..` would the debug format be dwarf-1?
>>
>> Of those, how many do we still support.
>
> 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. I wish I could say
> I will have the energy and time to maintain this in gdb but I just
> cant say that. Id be far more interested in getting it doing correct
> stack traces in 6.1 on SCO than in supporting DWARF1.
This confuses me a bit - what debugging format would you use
if Dwarf 1 were no longer available?
Stan
next prev parent reply other threads:[~2004-05-05 18:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2004-05-05 18:53 ` Kean Johnston
-- 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 22:01 Michael Elizabeth Chastain
2004-05-06 14:02 ` Andrew Cagney
2004-05-06 20:11 ` Mark Kettenis
2004-05-05 21:33 Michael Elizabeth Chastain
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=409932A9.3040504@apple.com \
--to=shebs@apple.com \
--cc=cagney@gnu.org \
--cc=ezannoni@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=jimb@redhat.com \
--cc=jkj@sco.com \
--cc=mec.gnu@mindspring.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