From: Michael Elizabeth Chastain <mec@shout.net>
To: ezannoni@redhat.com, gdb@sources.redhat.com
Subject: Re: gcov on gdb
Date: Tue, 07 Jan 2003 04:17:00 -0000 [thread overview]
Message-ID: <200301070417.h074HFs15628@duracef.shout.net> (raw)
Elena Zannoni writes:
> In doing so, I've noticed that a lot of lines in the stabread.c file
> are never executed because they are old functions (1996) to support
> cfront. I think we could obsolete this stuff. I've not found anything
> in a google search for cfront that was more recent than 1995.
More generally, I wish gdb had documentation about which compilers,
assemblers, and linkers that gdb supports, especially for C++.
Personally, I take the view that I prefer to test-bed gdb with other
Free Software. Specifically that means these licenses:
http://www.gnu.org/licenses/license-list.html#GPLCompatibleLicenses
http://www.gnu.org/licenses/license-list.html#GPLIncompatibleLicenses
I don't know what FSF policy is on this.
Michael C
apologies to elena z for the tangent on her thread
next reply other threads:[~2003-01-07 4:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-07 4:17 Michael Elizabeth Chastain [this message]
2003-01-07 4:24 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2003-01-07 2:22 Elena Zannoni
2003-01-07 4:26 ` Daniel Jacobowitz
2003-01-09 0:42 ` 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=200301070417.h074HFs15628@duracef.shout.net \
--to=mec@shout.net \
--cc=ezannoni@redhat.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