From: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: [PATCH 0.5/8] Rename "target child" to "target native".
Date: Mon, 17 Mar 2014 17:02:00 -0000 [thread overview]
Message-ID: <53272A8C.8080706@redhat.com> (raw)
In-Reply-To: <1395069784-7406-1-git-send-email-palves@redhat.com>
Whoop, pilot error...
On 03/17/2014 03:22 PM, Pedro Alves wrote:
> Pedro Alves (8):
> Rename "target djgpp" -> "target native"
> Rename "target darwin-child" -> "target native"
> Rename "target GNU" -> "target native"
> Windows: Rename "target child" -> "target native"
> nto-procfs.c: Add "target native".
> go32-nat.c: Don't override to_open.
> NEWS: Mention native target renames.
> Allow making GDB not automatically connect to the native target.
I missed including in the series the real patch #1, the one that
renames "target child" -> "target native". Here is is.
---
[PATCH 1/9] Rename "target child" to "target native".
I had been pondering renaming "target child" to something else.
"child" is a little lie in case of "attach", and not exactly very
clear to users, IMO. By best suggestion is "target native". If I
were to explain what "target child" is, I'd just start out with "it's
the native target" anyway. I was worrying a little that "native"
might be a lie too if some port comes up with a default target that
can run but is not really native, but I think that's a very minor
issue - we can consider that "native" really means the default built
in target that GDB supports, instead of saying that's the target that
debugs host native processes, if it turns out necessary.
This change doesn't affect users much, because "target child" results
in error today:
(gdb) target child
Use the "run" command to start a child process.
Other places "child" is visible:
(gdb) help target
...
List of target subcommands:
target child -- Child process (started by the "run" command)
target core -- Use a core file as a target
target exec -- Use an executable file as a target
...
(gdb) info target
Symbols from "/home/pedro/gdb/mygit/build/gdb/gdb".
Child process:
Using the running image of child Thread 0x7ffff7fc9740 (LWP 4818).
While running this, GDB does not access memory from...
...
These places will say "native" instead. I think that's a good thing.
gdb/
2014-03-17 Pedro Alves <palves@redhat.com>
* inf-child.c (inf_child_open): Remove mention of "child".
(inf_child_target): Rename target to "native" instead of "child".
gdb/testsuite/
2014-03-17 Pedro Alves <palves@redhat.com>
* gdb.base/default.exp: Test "target native" instead of "target
child".
---
gdb/inf-child.c | 8 ++++----
gdb/testsuite/gdb.base/default.exp | 4 ++--
2 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/gdb/inf-child.c b/gdb/inf-child.c
index 282467b..8a99adc 100644
--- a/gdb/inf-child.c
+++ b/gdb/inf-child.c
@@ -112,7 +112,7 @@ inf_child_prepare_to_store (struct target_ops *self,
static void
inf_child_open (char *arg, int from_tty)
{
- error (_("Use the \"run\" command to start a child process."));
+ error (_("Use the \"run\" command to start a process."));
}
static void
@@ -406,9 +406,9 @@ inf_child_target (void)
{
struct target_ops *t = XCNEW (struct target_ops);
- t->to_shortname = "child";
- t->to_longname = "Child process";
- t->to_doc = "Child process (started by the \"run\" command).";
+ t->to_shortname = "native";
+ t->to_longname = "Native process";
+ t->to_doc = "Native process (started by the \"run\" command).";
t->to_open = inf_child_open;
t->to_post_attach = inf_child_post_attach;
t->to_fetch_registers = inf_child_fetch_inferior_registers;
diff --git a/gdb/testsuite/gdb.base/default.exp b/gdb/testsuite/gdb.base/default.exp
index a39ffcf..3636fa3 100644
--- a/gdb/testsuite/gdb.base/default.exp
+++ b/gdb/testsuite/gdb.base/default.exp
@@ -746,8 +746,8 @@ gdb_test "step" "The program is not being run." "step #2"
#test symbol-file
gdb_test "symbol-file" ".*" "symbol-file"
-#test target child
-gdb_test "target child" "Use the \"run\" command to start a child process.*|Undefined target command: \"child\". *Try \"help target\".*" "target child"
+#test target native
+gdb_test "target native" "Use the \"run\" command to start a process.*|Undefined target command: \"child\". *Try \"help target\".*" "target native"
#test target core
send_gdb "target core\n"
--
1.7.11.7
next prev parent reply other threads:[~2014-03-17 17:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-17 15:23 [PATCH 0/8] Allow making GDB not automatically connect to the native target (and add "target native") Pedro Alves
2014-03-17 15:23 ` [PATCH 7/8] NEWS: Mention native target renames Pedro Alves
2014-03-17 16:45 ` Eli Zaretskii
2014-03-17 15:23 ` [PATCH 6/8] go32-nat.c: Don't override to_open Pedro Alves
2014-03-17 16:44 ` Eli Zaretskii
2014-03-17 15:23 ` [PATCH 1/8] Rename "target djgpp" -> "target native" Pedro Alves
2014-03-17 16:44 ` Eli Zaretskii
2014-03-17 15:23 ` [PATCH 4/8] Windows: Rename "target child" " Pedro Alves
2014-03-17 15:23 ` [PATCH 8/8] Allow making GDB not automatically connect to the native target Pedro Alves
2014-03-17 16:47 ` Eli Zaretskii
2014-03-18 21:55 ` Stan Shebs
2014-03-25 20:06 ` Doug Evans
2014-05-21 17:53 ` Pedro Alves
2014-06-03 5:35 ` [PATCH OBV] Fix a regexp pattern in gdb.base/auto-connect-native-target.exp (Re: [PATCH 8/8] Allow making GDB not automatically connect to the native target.) Yao Qi
2014-03-17 15:23 ` [PATCH 3/8] Rename "target GNU" -> "target native" Pedro Alves
2014-03-17 15:23 ` [PATCH 2/8] Rename "target darwin-child" " Pedro Alves
2014-03-17 15:23 ` [PATCH 5/8] nto-procfs.c: Add " Pedro Alves
2014-03-17 17:01 ` [PATCH 0.5/8] Rename "target child" to " Pedro Alves
2014-03-17 17:02 ` Pedro Alves [this message]
2014-06-03 5:29 ` [PATCH OBV] Fix regexp pattern in gdb.base/default.exp (Re: [PATCH 0.5/8] Rename "target child" to "target native".) Yao Qi
2014-05-21 17:57 ` [pushed] Re: [PATCH 0/8] Allow making GDB not automatically connect to the native target (and add "target native") Pedro Alves
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=53272A8C.8080706@redhat.com \
--to=palves@redhat.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