From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: GDB Speak: `inferior' rather than `target'?
Date: Mon, 02 Dec 2002 13:20:00 -0000 [thread overview]
Message-ID: <20021202212046.GA23744@nevyn.them.org> (raw)
In-Reply-To: <3DEBC4AB.9020706@redhat.com>
On Mon, Dec 02, 2002 at 03:38:03PM -0500, Andrew Cagney wrote:
> Hello,
>
> In trying to correctly and clearly word some gdb comments (and yes ok,
> and internal doco), I'm left wondering if we should `newspeak' some
> terminology here and use the word `inferior' instead of `target'.
>
> The problem with `target' is that it is totally overloaded. The
> configuration target, the running target the target architecture, ....
>
> Hence, when refering to an instance of the program being debugged, the
> word `inferior' should be used. Of course, this would mean that `core'
> becomes an inferior (...).
I've always used inferior only for a running target, generally a
ptraced one locally. But that's just my usage.
I'm with Kevin - I don't like either inferior or target. I'd suggest
punting to debugee but it's too cumbersome.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-12-02 21:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-02 12:38 Andrew Cagney
2002-12-02 12:44 ` Kevin Buettner
2002-12-02 22:02 ` Eli Zaretskii
2002-12-02 13:20 ` Daniel Jacobowitz [this message]
2002-12-02 13:30 ` Andrew Cagney
2002-12-02 22:22 ` Felix Lee
2002-12-03 5:29 ` Peter Reilley
2002-12-03 6:24 ` Stan Shebs
2003-02-02 6:39 ` Andrew Cagney
2002-12-02 21:07 Nathanael Nerode
2002-12-02 21:22 ` Daniel Jacobowitz
[not found] <redirect-4680177@silicondust.com>
2002-12-02 22:32 ` Nick Kelsey
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=20021202212046.GA23744@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@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