From: Stan Shebs <stan@codesourcery.com>
To: gdb-patches@sourceware.org
Subject: Re: [RFA] make first parameter of to_lookup_symbol const char *
Date: Wed, 16 Mar 2011 20:03:00 -0000 [thread overview]
Message-ID: <4D8116B1.90605@codesourcery.com> (raw)
In-Reply-To: <20110316135810.GA6590@adacore.com>
On 3/16/11 6:58 AM, Joel Brobecker wrote:
>>> BTW, it looks like no target defines this operation...
>> Unless you use it for some new patch of yours it should be removed instead.
> This is what it looks like to remove the target_ops method. It feels
> a little like excising a potentially useful feature, so I'm not going
> to commit without review, although there is no sign that we'll ever
> need it any time soon. But I added a comment explaining what we used
> to do, to give us a clue later on, if we encounter a target where
> we might need something of this kind.
Yeah, it looks like the last use quietly evaporated with the deletion of
remote-vx.c in 2004.
Features without any means of exercise are likely to bitrot semantically
even if they continue to compile/run (witness tracepoints), so it's in
our interest to be ruthless.
I used to have fun using gcov with the GDB testsuite to find segments of
code that were never exercised - gcov results are cumulative, so the
post-testing coverage display is good for ideas as to what test cases
ought to be written, and also suggests code that might turn out to be
intrinsically unreachable.
Perhaps msnyder can play with that when he gets tired of coverity. :-)
Stan
next prev parent reply other threads:[~2011-03-16 19:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 11:56 Tristan Gingold
2011-03-14 13:53 ` Jan Kratochvil
2011-03-16 14:02 ` Joel Brobecker
2011-03-16 15:03 ` Tom Tromey
2011-03-16 20:03 ` Stan Shebs [this message]
2011-03-17 14:58 ` Joel Brobecker
2011-03-14 14:03 ` Pedro Alves
2011-03-14 14:21 ` Tristan Gingold
2011-03-15 8:26 ` Joel Brobecker
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=4D8116B1.90605@codesourcery.com \
--to=stan@codesourcery.com \
--cc=gdb-patches@sourceware.org \
/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