From: David Carlton <carlton@math.stanford.edu>
To: Andrew Cagney <ac131313@redhat.com>
Cc: Daniel Jacobowitz <drow@mvista.com>, gdb-patches@sources.redhat.com
Subject: Re: PATCH: Remove ancient GNU catch catch/catch throw support
Date: Mon, 14 Apr 2003 20:12:00 -0000 [thread overview]
Message-ID: <ro1d6joet4m.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <3E807451.6050009@redhat.com>
[ Going through old e-mail. ]
On Tue, 25 Mar 2003 10:22:57 -0500, Andrew Cagney <ac131313@redhat.com> said:
>> This is for either g++ 1.x or early 2.x; it doesn't work for 2.95 which is
>> the oldest C++ compiler we're interested in supporting. I'll commit this in
>> a day or so unless anyone has a good reason not to.
> The statement that GDB doesn't support anything before 2.95 should
> also be formalized. At present there isn't anything in writing :-(
There is the following statement in gdb.texinfo:
Currently, @value{GDBN} works best when debugging C@t{++} code that
is compiled with @value{NGCC} 2.95.3 or with @value{NGCC} 3.1 or
newer, using the options @option{-gdwarf-2} or @option{-gstabs+}.
DWARF 2 is preferred over stabs+. Most configurations of
@value{NGCC} emit either DWARF 2 or stabs+ as their default debug
format, so you usually don't need to specify a debug format
explicitly. Other compilers and/or debug formats are likely to work
badly or not at all when using @value{GDBN} to debug C@t{++} code.
But it probably should be mentioned more prominently somewhere. I'm
not sure exactly what we want to say: we're not going through and
ripping out support for HP's C++ compiler, after all. (At least not
yet...)
David Carlton
carlton@math.stanford.edu
next prev parent reply other threads:[~2003-04-14 20:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-25 3:05 Daniel Jacobowitz
2003-03-25 15:23 ` Andrew Cagney
2003-04-14 20:12 ` David Carlton [this message]
2003-03-26 20:19 ` Daniel Jacobowitz
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=ro1d6joet4m.fsf@jackfruit.Stanford.EDU \
--to=carlton@math.stanford.edu \
--cc=ac131313@redhat.com \
--cc=drow@mvista.com \
--cc=gdb-patches@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