From: Daniel Jacobowitz <drow@mvista.com>
To: gdb <gdb@sources.redhat.com>
Subject: Re: GDB DWARF-1 C++ support
Date: Fri, 17 Jan 2003 19:56:00 -0000 [thread overview]
Message-ID: <20030117195635.GA13418@nevyn.them.org> (raw)
In-Reply-To: <ro17kd33624.fsf@jackfruit.Stanford.EDU>
On Fri, Jan 17, 2003 at 11:54:59AM -0800, David Carlton wrote:
> [ I've retitled this bit of the thread and moved it to gdb@. ]
>
> On Fri, 17 Jan 2003 13:28:08 -0600, Michael Elizabeth Chastain <mec@shout.net> said:
>
> > Here is what I want to do about gdb DWARF-1 C++ support:
>
> > make a policy decision whether gdb supports DWARF-1 with C++
>
> > if yes:
> > remove all the setup_xfail_format DWARF-1 calls
> > add regular DWARF-1 testing
> > file about 50 new PR's for all the new FAIL's
> > file PR's against gcc for the external bugs (and they will hate us)
>
> > if no:
> > document that gdb supports C++ with DWARF-2 or stabs+ but not DWARF-1
> > add a DWARF-1 check to "skip_cplus_tests"
> > remove all the setup_xfail_format DWARF-1 calls
>
> Yup. I'm not familiar with DWARF-1, so conceivably it's possible
> that we want to support C++ DWARF-1 debugging but that DWARF-1 is by
> nature incapable of supporting the full range of C++ features, in
> which case we'd only skip certain C++ tests under DWARF-1. But I'm
> really not worried about that possibility for now.
>
> Anyways, my kneejerk reaction is that no, we shouldn't support it: I
> have a hard time imagining a scenario where it would be a profitable
> use of resources to work on supporting DWARF-1. What platforms use it
> as their native debugging format? What C++ compilers run on those
> platforms?
I believe no recent version of GCC uses DWARF-1 that does not also
support DWARF-2. We support oddball C compilers, but not oddball C++
compilers, in general.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-01-17 19:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200301171928.h0HJS8805276@duracef.shout.net>
2003-01-17 19:55 ` David Carlton
2003-01-17 19:56 ` Daniel Jacobowitz [this message]
2003-01-18 6:19 ` Daniel Berlin
2003-01-17 20:07 ` Elena Zannoni
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=20030117195635.GA13418@nevyn.them.org \
--to=drow@mvista.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